You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
From Cidney on Discord:
Right now it looks like the player always walks towards the ESCItem when clicked (either the center of the item or a waypoint). If the ESCItem isn't reachable (say, you're looking at the sky) and there's no waypoint in the walkable area, it fails silently. This is getting to a be a bit of an annoyance.
Usually in adventure games the player only moves to use, not to look. Is it possible to give the designer more control over this?
Describe the solution you'd like
2 proposals:
either we remove completely the player walking automatically towards the ESCItem and it's then required to code the walk on the ESC script
either we add a parameter to ESCItem to enable or disable automatic walking (and if disabled, then it is also required to explicitly add a walk command in the ESC script)
Solution 2 would have our preference. However we need to think of hybrid cases where we want look action to not walk towards object, and other actions to walk towards it. One parameter may not be sufficient here.
Describe alternatives you've considered
See above
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
From Cidney on Discord:
Describe the solution you'd like
2 proposals:
Solution 2 would have our preference.
However we need to think of hybrid cases where we want
look
action to not walk towards object, and other actions to walk towards it. One parameter may not be sufficient here.Describe alternatives you've considered
See above
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: