The error in the software is, that if you are trying to see if an object is not at a specific x and y coordinate the software is by default checking x or y. Which checks the whole x axis and the whole y axis instead of a specific x and y coordinate. So I can’t find any way to check if an object is not at a specific x and y coordinate. I need this fixed asap. Can someone please tell me how to report this issue?
While it’s possible to be a bug, what you’re describing doesn’t sound like an engine issue and sounds more-so a logic issue.
Before anyone could treat it as a bug, you will have to show screenshots of the event actions and conditions you’re attempting to use in order for everyone to help.
Here is an image of the code I am using. It states that if the tile is dropped in the same spot do one thing. And if the tile is not dropped in the same spot do something else. But if the tile is dropped on the same x or y axis it doesn’t do the something else. But if the tile is dropped any where not on the same x axis or y axis it does the something else. When I actually want it to do the something else as long as the tile is not dropped at the same x and y coordinate. Hopefully this helps. If you need anything else let me know.
Let’s say there is:
- a red square
- a red circle
- a green square
- a green circle
if you take the shapes that are red and square, the negation is not the shapes that are not red and not square because you would only get a green circle where you want everything except the red square.
I am not sure what you are saying. Could you explain what you are saying a little better, please?
I meant that your conditions on X and Y in the 2nd event is not the negation of the ones in the 1st event.
It looks like you were trying to do a negation but maybe I don’t understand what you want to do.
Yeah, that sounds like a frustrating limitation. It makes sense that checking just x or y independently would cause issues instead of verifying both together. You might want to report this on the official GDevelop GitHub issues page or their community forums—just describe the bug clearly with an example.
No need to, this is not a bug of GDevelop. The issue is very probably they don’t know how boolean logic works.
1 Like
It looks like your second event is checking if it is both not on the X-axis AND not in the Y-axis. If you add an Or to it it’ll work. So it should be:
BCrystal was just dropped
OR Condition
>X Position of BCrystal != BCrystalOldX
>Y Position of BCrystal != BCrystalOldY
The OR condition is under Advanced > Events and Control Flow in the conditions list
1 Like