Point & Click - Dysfunctional Collisions & Movement (v2>v3)

[Geonjaha]

In point n click mode, I had locked movement in each direction by binding a key to move 3 tiles each time, and used collisions to prevent movement outside the UI shown.

Now (in converting to v3), the movement seems to be back to being unlocked (or the underlying movement wasn't overwritten by the script attached to the button), and the collision boundaries also seem very ineffective.

Gif shows before (v2) and after (v3)

Image below shows the collision boundaries (both versions)

Image below shows the scripts used for movement. Same respectively for all four directions

Platform:

• OS: Windows 10 Pro
• GB Studio V3.0

[RichardULZ]

Note that per tile map collision was never part of point and click (though i don't see why it shouldn't be? Would be really useful).

Otherwise it's most likely doing both the default movement of pointandclick, plus the scripted movement.

Wether this is solved by removing (or having the option to remove) default functionality of a button with attached script (used to be in 2.0), or another event that stops player movement, needs to be investigated.

[maxoakland]

I agree that tile collisions should be part of point & click mode

[gmarty]

Yes, tile collisions should part of point and click mode.
Hopefully you can still opt out of collisions and get the current behaviour by adding a Set Actor Collisions Disable on the player (cursor).

There is this use case where you want to be able to move the cursor anywhere on the screen, but actors must still conform to collisions when they move, a la Maniac Mansion.