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
When moving into a space that produces a 0 (like moving into a block of MBL) the getMoveCount function does not return a 0 (though we see the 0 on-screen.)
If doing so goes against expected "default" behaviour (and it probably does) I'd like to see a parameter that will return the 0 value when a token is making an "illegal" move.
The Solution you'd like
Add a third option for the first parameter of getMoveCount().
Right now we have:
0 for normal count (default);
1 for fractional movement - only valid with 1-2-1 movement metric
A "2 for smart movement value" (or whatever it's called) would work.
Alternatives that you've considered.
A new function to return the "smart" movement value.
Additional Context
If we had this, people could disallow movement into "0" spaces easily in an onTokenMove. Disallowing this kind of movement is a common request and this would be a simple solution.
The text was updated successfully, but these errors were encountered:
Describe the Problem
When moving into a space that produces a 0 (like moving into a block of MBL) the getMoveCount function does not return a 0 (though we see the 0 on-screen.)
If doing so goes against expected "default" behaviour (and it probably does) I'd like to see a parameter that will return the 0 value when a token is making an "illegal" move.
The Solution you'd like
Add a third option for the first parameter of getMoveCount().
Right now we have:
0 for normal count (default);
1 for fractional movement - only valid with 1-2-1 movement metric
A "2 for smart movement value" (or whatever it's called) would work.
Alternatives that you've considered.
A new function to return the "smart" movement value.
Additional Context
If we had this, people could disallow movement into "0" spaces easily in an onTokenMove. Disallowing this kind of movement is a common request and this would be a simple solution.
The text was updated successfully, but these errors were encountered: