Public Warp Configs Wiped on restart and reload.
StoneLegion opened this issue ยท 8 comments
Build: 69
First off I delete my configs while the server is offline and start the server up. Once the first person logins the default configs are generated. You now have the default unlimited quota's and such. I create /warp set test public.
I check the config file and it works wonderful.
I shutdown the server and start it up and it replaces the config files back down to 10kb. With the following config:
warps:
warps: {}
Config:
quotas:
public: 0
private: 0
players:
- Kane_Hart
Now I can reset quota with the command and change it back to unlimited but hehe. Everytime I reboot it I gotta redo it.
So in the end:
Reload resets public warps, quota's but private warps /home and such stay fine.
Here is what a warp file looks like right when I set a warp.
warps:
test:
yaw: 89.70047
owner: Kane_Hart
pitch: 21.149973
z: 28.46875
world: build
y: 108.0
x: 47.6875
With the following warps.yml
warps:
water:
yaw: 314
owner: NVX
pitch: 11
z: -76.1753582949035
world: world
y: 63.0
x: 196.076489186934
atlantis:
yaw: -271
owner: Vektah
pitch: 9
z: -695.160329025851
world: world
y: 52.0
x: 211.775865552362
cannon:
yaw: 924
owner: NVX
pitch: 24
z: -23.7144601347932
world: world
y: 76.0
x: 281.754906811625
warehouse:
yaw: -185
owner: NVX
pitch: -4
z: -231.220870407111
world: world
y: 70.0
x: 339.138882224268
store:
yaw: -1
owner: NVX
pitch: 10
z: 51.9505370901113
world: world
y: 73.0
x: 45.5336634342277
shop:
yaw: -1
owner: NVX
pitch: 10
z: 51.9375
world: world
y: 73.0
x: 45.53125
sandmine:
yaw: 35
owner: NVX
pitch: 34
z: -980.652351379791
world: world
y: 74.0
x: 302.551693173741
cleanroom:
yaw: 5
owner: NVX
pitch: 14
z: 0.0
world: cleanroom
y: 65.0
x: 0.0
I experience similar issues (warps.yml wiping) but if I remove the cleanroom warp, the issues appear to go away. Possibly an issue with unloaded worlds (when testing I was the only player online, and I was in the "world" world).
The warnings from Issue #22 occur as well, so could possibly be related.
Is this a duplicate of #22?
I believe this should be fixed along with the fix for #22 - I no longer experience the issue described in here, once KaneHart verifies I'd close both :)
Damnit, why can't Multiverse have intelligent bug discussions like OpenWarp does... sigh