SpoutDev/Spout — Issue #1374: Multiverse spawning issues with spout.
Author: andrewkm
Created: 2012-01-01 01:31:54+00:00
State: open

Work around was done here:
https://github.com/Multiverse/Multiverse-Core/commit/9f12f6362b72850c25a6a0fa058e5d82f1aef748

Basically whenever new players join they would go to the world spawn immediately and last locations are never saved. MV made a work around for this above.

----------
This adds a new config var: firstspawnoverride that defaults to true.
You should disable this if you don't want mv to do your spawning (if
you have Spout, a warning will print and it will be disabled
automatically. The firstspawn feature will NOT work with spout at this
time.) When the spout bug is fixed, someone should open an issue. I
will not be monitoring this :)
-----------

Console showing the following therefore im making this issue.
2011-12-31 18:51:42 [WARNING] [Multiverse-Core] Disabling MV's 'firstspawnoverride', since spout doesn't handle new players well yet.
2011-12-31 18:51:42 [WARNING] [Multiverse-Core] This means *new players* may not spawn where you've set your "mvspawn" AND
2011-12-31 18:51:42 [WARNING] [Multiverse-Core] the config value 'firstspawnworld' will have NO effect!!!
2011-12-31 18:51:42 [WARNING] [Multiverse-Core] Talk to the Spout devs to get this fixed!
2011-12-31 18:51:42 [WARNING] [Multiverse-Core] --FernFerret