-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WorldBorder turbo fill command does not work and ram issues #412
Comments
The filler is threaded now. There is no need for turbo/autopilot anymore. |
So this is already in the build I use? |
I' have to do some research on that. I cant find a good way.to unload chuncks..... |
Maybe you could try to look into the WorldBorder Source (Bukkit Plugin). Hope you can find a solution for that! :) |
There is no chunck code in chickenchuncks, it just uses ForgeChunkManager which is only for chunckloading. |
Should be fixed in latest versions of FE. |
How can that be fixed when I reported the bug for the latest version? |
171 is latest build. |
Oh you mean the dev/beta builds. Thanks will look into it. |
Sorry but how does this work now?
TW folder is DIM7. Edit: Edit2:
|
codechicken.chunkloader.PlayerChunkViewerManager.calculateChunkChanges(PlayerChunkViewerManager.java:155) That is not my code. It if caused by the filler, but there is nothing we can do about it. |
Well but it worked until you "fixed" it... Just with ram issues ;) What about the first error now? How to start it in other dimensions than the overworld? |
Whenever I try to use "/worldborder turbo" or "/wb turbo" it says that the command is unknown.
Tried both console and ingame. Using Build 1.1.1.251
Also it would be nice if you can set the speed in the command.
Example:
/wb turbo 20 (20 chunks per tick. If you define nothing it will use the default 10x speed)
Second thing:
The fill commands eats all assigned ram. It will not clear it and just stop generating chunks after some minutes (depends on how much you assigned).
After 5 minutes: 56.0MB/952.0MB (5%) free (Also tried with 3GB, same happened)
I tried it with 500 chunks only, which worked, but it doesn't clear up the ram after it finished the job.
So you are forced to restart the server if you want to clear up your ram.
The text was updated successfully, but these errors were encountered: