virtualx-engine/demos/2d/space_shooter/shot.gd
Rémi Verschelde 7589b2bf60 Improve code formatting
The scripts were streamlined using more or less the following conventions:
 - space after a comma in lists of arguments
 - spaces around weak operators (+, -), no spaces around strong operators (*, /)
 - spaces around comparison operators and compound assignment operators
 - space after a comment start (#)
 - removed trailing spaces or tabs, apart from those that delimit the function indentation level (those could be removed too but since they are added automatically by the editor when typing code, keeping them for now)
 - function blocks separate by two newlines
 - comment sentences start with an upper-case letter
2015-12-09 08:39:12 +01:00

41 lines
583 B
GDScript

extends Area2D
# Member variables
const SPEED = 800
var hit = false
func _process(delta):
translate(Vector2(delta*SPEED, 0))
func _ready():
# Initialization here
set_process(true)
func _hit_something():
if (hit):
return
hit = true
set_process(false)
get_node("anim").play("splash")
func _on_visibility_exit_screen():
queue_free()
func _on_shot_area_enter(area):
# Hit an enemy or asteroid
if (area.has_method("destroy")):
# Duck typing at it's best
area.destroy()
_hit_something()
func _on_shot_body_enter(body):
# Hit the tilemap
_hit_something()