WORLDGUARD-2736 - Reported by Llarlen

Let's say a player's in an area he's not allowed to leave. We can then

1. change the player's group, so he's allowed to leave (theoretically)
2. change the region's setting so everyone's allowed to leave (theoretically)
   since it's always checked against the state of being allowed to leave of the previous position and such changes take place without the player changing position, the player will get stuck until one does a /wg flushstates. The problem with this approach is though, that any other tests that depend on states will be broken for a short moment. So a player pushing against an exit blocked boundary will be able to get out in that moment.

The only fix I see here is to check being allowed to exit on previous and current position with current permissions instead of carrying over the last test.

Comment by Llarlen

Sorry, got ahead of myself. Flushing states is no problem. It's just uncommon to require to do this after an exit permission change.

Comment by wizjany

you can do /wg flushstates
even better, use commandhelper to tie together your permissions group changing commands with it

Comment by sk89q

Closing this issue due to age. If someone is still interested in this issue, please make a new one or ask this one to be re-opened.