Limework
/
FastWorldReset
2
1
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Make stuff more informative

This commit is contained in:
Govindas 2021-02-13 16:41:04 +02:00
parent eeedc05b43
commit ca18edb0c3
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
fastworldreset.sk
View File

@ -682,7 +682,7 @@ command /fastworldreset [<text>] [<text>] [<text>]:
else:
send "&2&l--=-= &a&lFastWorldReset Commands &2&l=-=--"
send "&f/fwr create <world> [generator] &a- Add a world to FastWorldReset system or create a completely new world into the system."
send "&f/fwr create <world> [generator] &a- Add a world to FastWorldReset system or create a completely new world into the system. (Or update existing world's template)"
send "&f/fwr delete <world> &a- Removes the world from FastWorldReset system, does not unload or delete the world."
send "&f/fwr clone <world> <new-world> &a- Clones a FWR world."
send "&f/fwr reset <world> &a- to reset a world. (Must be in FastWorldReset system)"
@ -771,8 +771,8 @@ on world init:
set {_config}.autoSavePeriod to 0
set {_config}.maxAutoSaveChunksPerTick to 0
#needed, because if it is set as true... entity ticking may totally bug out with the way FastWorldReset's chunk-based reset mehod works
#it may sometimes cause behavior like projectiles constantly teleporting back and never landing if set to true
#in the past I thought this is needed, now I am not sure as I haven't noticed a difference, but I'll keep it here, just in case, it sounds logical to disable it for chunk-based reset
set {_config}.skipEntityTickingInChunksScheduledForUnload to false
event-world.setKeepSpawnInMemory(false)