ALT: Annoyed Anime Girl's Tired Expression

This week's segment include The Business Side (A discussion of industry moves: acquisitions, layoffs, subscription service strategies, market trends, unionization efforts, or stock performance) and Ha

YouTube video by Rounding Off Infinity

It’s really easy using signals to do what you want without exporting a method. At some point signals started showing up in the editor when you create them. Here’s a screen shot from a game I’m working on now. Both LevelSelect and UIScreen are custom classes. Based on your screenshots, do something like this: class_name InputComponent extends Node signal input_received(direction: Vector2) func _physics_process(delta: float) -> void: var direction := vector2.ZERO var direction2 = Input.get_vector("move_left", "move_right","move_up","move_down") input_received.emit(direction) class_name MoveComponenet extends Node @export var actor: Node2D @export var speed := 1.0 func _on_input_received(direction: Vector2) -> void: actor.position += direction * speed Then you can hook it up in the editor like any other signal, or add this to you MoveComponent code: @onready var input_component = "$../InputComponent" func _ready() -> void: input_component.input_received.connect(_on_input_received) Personally, I add a parent component that handles all the signals like a switchboard. But you may be doing something slightly different than I am, as I have the inputs inside each state, and if the state isn’t in the tree, that things can’t be done.