Two Area2Ds - one entry signal - collision disabled - (SOLVED)

SnapCracklins

So I have 2 area2d's for this simple whack-a-mole game that I am building. My hammer is an Area2D and my moles are Area2D. I have global variables in my AutoLoad for determining Hits and when Moles register as Hit. The script is supposed to trigger an animation change and register a hit whenever the Area2D is entered by the hammer and when the "ui_accept" is pressed. Signal is not executing like it should.

My hammer is an Area2D with Sprite and CollisionShape2D as child nodes. My mole is an Area2D with AnimatedSprite and C ollisionShape2D as child nodes.

I am using mouse-hover as control so obviously I don't want the bodies to collide.

Moles Script: (enemy object)

Hammer Script: (player object)

And here's the AutoLoad though I don't think the Globals are affecting this?

Help appreciated if I don't solve it by then.

GlyphTheWolf

Hi,

I don't understand exactly what the problem is, but one thing I see is that when you have something like that:

var hitting = Global.isHitting

Then you just copy value of the Global.isHitting at the time when your scene is created.

Since your Global.isHitting will be just boolean (simple type) then it will be probably just copied, so later when you set:

hitting = true

It doesn't change value stored in singleton. It would be different if that would be more advanced type like Array or Dictionary then it would be passed by reference and work more as you expect.

Anyway I have no idea if that is something connected with issue you ask about, because it is not connected with sending signals.

SnapCracklins

Well that helped and I got it to trigger once but it's still not trigger the enemy on the "whack" button. Changed to direct global variable calls.

Hammer object: Moles object:

SnapCracklins

Here is an error code:

E 0:00:00.870 emit_signal: Error calling method from signal 'area_entered': 'Area2D(Moles.gd)::_on_Moles_area_entered': Method not found.. <C++ Source> core/object.cpp:1236 @ emit_signal()

Am i using signals wrong?

SnapCracklins

Okay. Kudos @GlyphTheWolf for nailing it. The global variables are what messed me up. Changed some to local (including the hit check) and made a signal from the hammer instead to trigger a "canHit" variable. NOW it's working. :blush:

Thank you for the patience and expertise.

SOLUTION: Hammer object: Mole Object: