#Why is a signal being emitted regardless of which area my player hits?

1 messages · Page 1 of 1 (latest)

prisma remnant
#

could you do a full screenshot?

#

I mean I have a solution but its real hard you only have smal pieces

#

I can't look for all of them

#

for my current solution I suggest you make it so the area joe detect the player instead of player detecting the table

#

ok so this is whats happening

#

player is detects one

#

and since its in all one player it emits both of them

#

you should make the dectector in the tables

#

or declare what your tryna hit

#

its like if player does smth the signal says it will emit everything it was said to do

#

if the player enter a area the signal will emit both of them

#

umm I suggest use visibillty

#

instead of show and hide

#

button_name.visiblitty = false or true

#

in the table don script use $donbutton.visiblity = false or true

#

I suggest you to experiment with the properties editing in script $something.property or function

#

cause those are important mostly in game development

#

are you using the main player script or the world script

#

create a script for the main world

#

then you can access it

#

then put the signal into the

#

like the root node

#

put it there so it can access every thing

#

will it emits if something happen of what it says and like heres the thing player entered the area it will emit the signal since you connected both table to it. it will emit to both of them

#

you should learn the area2D like declarify smth where if it enters the area2D it also check for the area2d name you said and it can access its property this is mostly used for damage system

#

well I have a video for it

#

oh you could use .visibillty = true or false but I guess that works it didn't work or didn't have the function in gd 3.5 and 3.4

#

https://www.youtube.com/watch?v=mdhKQLUHm2s

YouTube
John Ivess
Hit- and Hurtboxes + Collision Layers explained (Combat Essentials ...

In this episode of the Combat Essentials course, we'll cover setting up functional Hitboxes and Hurtboxes, and Collision Layers, which allow you to virtuously manage all your collisions.

PROJECT REPO: https://github.com/IvessJohn/combat-done-right-godot

o_lobster, the artist who provided me his asset pack: @sir_shazam https://o-lobster.itch.io...

▶ Play video
#

its same I guess but like its taking the property and setting it to what you want not saying like make that true or false

#

theres a visbillty property in every node

#

this .visibllity changes it

#

to what you want

#

false or true

#

in other words 0 or 1

#

gd 4 was a suprise for me everything was reworked

#

if you used godot before 4 you know character body wasn't always here before gd 4 its called kinematic body 2D

#

I mean not that much changed except in scripting I was having trouble going to learn everything

#

yea I was like hold up when the update came bro this bugged where kinematic

prisma remnant
#

and the new movement feature

#

where it gets the axis

#

and stuff I had to relearn

#

also the tile map

#

I had to watch 5 tutorials

#

for colllision

#

and tryna get my tiles

#

like @export var int doesn't work anymore

#

I had to do @export var only

#

whats the game your working on about?

#

ohh

#

thats easy I think

#

just finished the small parts scence and add it into the main world game