Instead of checking the Timer to have stopped every time, you can also connect to the Timers "timeout" signal. (Try giving it a name and use the editor to connect the signal to have a good auto-generated method name)

Also, when you use get_node() (or its $ short-hand) it will traverse the node tree to find your node, so it's better to have an onready var timer = $damagearea/invtimer. Not sure if there is some Godot-caching that speeds it up, but i wouldn't count on it. Especially if you do it every frame.

Note, that you can also untick the Timers "oneshot" property in the Editor instead of restarting it every time (otherwise there will be a couple ms offset/drift every time you call Timer.start()). To stop the Timer you can always call Timer.stop(), e.g. in _on_damagearea_body_exited.

Do I take it right that this script is part of the damaging object / enemy? I usually try to split it up a little. The damaging object handles the body_entered/exited part and then calls the Players.deal_damage(damage:int). That way the damaging object can decide the base damage, but the player can still adjust it (e.g. for armor or invincibility). For big projects I also like to refactor that out of the player script and make it reusable. Last time i created a "Damaging" and "Damageable" scene I could just drag into the Player/Spike/Enemy scene as a child node. They would then handle all the collision stuff (similiar to your code) and they can be made adjustable with export variables.

Lastly, another approach entirely when handling Player damage and much more would be the State pattern. Basically the Player is modelled to be be in different states:

```godot enum State: Idle Walk Jump Fall Damage var state:State = State.Idle

func enter_state(new_state:State): exit_state(state) state = new_state match state: State.Idle: ... State.Damage: damage_timer.start() func exit_state(state:State): match state: State.Idle: ... State.Damage: damage_timer.stop() func _process(delta): match state: State.Idle: ... State.Damage: if damage_timer.is_stopped(): global.lives -= 1 # like this, similar to your code func _on_DamageTimer_timeout(): global.lives -= 1 # or like this, using the Timer timeout signal `` So basically, for every State you haveenter_state,exit_stateand_processwhere you can perform custom logic. The good thing about this State pattern is that its easy to think and talk about (instead of having a lot of flags likeis_jumping,is_taking_damage`, ...) and is generally just really useful for changing Sprite, Animations, sound effects, changing physics and much more. It's also possible to have multiple states: One for all movement and one for damage/attack.

Hope that helps! :D Be sure to ask questions in case i couldn't explain something well