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
As of #381, the reroll command uses our now-standard actor-threading behavior (it requires an actor
and only applies the change if the current actor matches the last node's actor), but it doesn't need to work this way. It could apply to ANY move in the final position, regardless of whose
actor node it is in. What's the right behavior here?
The text was updated successfully, but these errors were encountered:
As of #381, the reroll command uses our now-standard actor-threading behavior (it requires an actor
and only applies the change if the current actor matches the last node's actor), but it doesn't
need to work this way. It could apply to ANY move in the final position, regardless of whose
actor node it is in. What's the right behavior here?
The text was updated successfully, but these errors were encountered: