by Admiral Ackguh » Tue Jul 28, 2015 8:22 pm
One of the uses of the SUCCESS variable is to block the player from traversing a portal, by using the portal's passing action macro to set SUCCESS to 0.
If the player is unburdened, everything works as expected.
If the player is burdened: The game engine runs the step macro one or more times after the portal macro, and sets SUCCESS to 1 before each step macro call, and checks SUCCESS after each call.
That means that a burdened player can use portals that should be blocked.
Solution: Obviously, the step macros must change SUCCESS in the same way as the portal macros. The developer could duplicate portal macro code, or set aside a variable for "global success". If so, Portal macros would need to set this variable the same way as SUCCESS, and step macros would set SUCCESS to this variable.
One of the uses of the SUCCESS variable is to block the player from traversing a portal, by using the portal's passing action macro to set SUCCESS to 0.
If the player is unburdened, everything works as expected.
If the player is burdened: The game engine runs the step macro one or more times after the portal macro, and sets SUCCESS to 1 before each step macro call, and checks SUCCESS after each call.
That means that a burdened player can use portals that should be blocked.
Solution: Obviously, the step macros must change SUCCESS in the same way as the portal macros. The developer could duplicate portal macro code, or set aside a variable for "global success". If so, Portal macros would need to set this variable the same way as SUCCESS, and step macros would set SUCCESS to this variable.