Closed bitflipr closed 12 years ago
Interesting. I was unaware we were doing this. maybe @main-- can look at it soon, but if not, I'll have a peek tomorrow. I'm reworking some of the portals perms to provide better feedback to users, and this may help debugging this issue.
Let me know if you need any assistance in reproducing this bug. I'll keep an eye out for any resolution to this.
I was a bit lazy so I decided to use the easiest workaround for #7: Reloading Portals.
Should be working fine in latest build: http://ci.onarandombox.com/job/Multiverse-Adventure/527/
I've observed that permissions to multiverse portals (multiverse.portal.access.*) are not observed when Multiverse-Adventure resets an adventure world after it was visited.
I'm guessing that since Multiverse-Adventure forces Multiverse-Portals to reload during runtime that there is a bug in the code that prevents permissions from being followed.
Log snippet:
20:09:15 [INFO] [Multiverse-Adventure] Reset of world 'COTPP' finished. 20:09:15 [INFO] [Multiverse-Adventure] Reloading Multiverse-Portals to make it use the changed world. 20:09:15 [INFO] [Multiverse-Portals] 7 - Portals(s) loaded
Note that the portals are not even located in the reset world.