SL21W52: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 9: | Line 9: | ||
**Create FakeChunks from Anti-XRay chunk data only | **Create FakeChunks from Anti-XRay chunk data only | ||
**Cleanup FakeviewDistance Codes, Move away from PlayerChunkMap | **Cleanup FakeviewDistance Codes, Move away from PlayerChunkMap | ||
* | *Feature: Change implementation of commands to fully async | ||
** | **Bukkit for some reason wants all commands to be sync by default. We do not want that! | ||
*Test Chatterino | *Test Chatterino | ||
*Feature: /user playerrenderdistance | *Feature: /user playerrenderdistance | ||
*Feature: /user entityrenderdistance | *Feature: /user entityrenderdistance | ||
* | *Bug: RecentTPS is not updated correctly, check updateTicks in MinecraftServer | ||
* | * | ||
* | * | ||
* | *Bug: Desktop slow if the Minecraft-Server is slow? Why? | ||
**Test with a lot of hoppers running in the background | **Test with a lot of hoppers running in the background | ||
*Test: Chunkli insert was super slow when testing fake-view distance? Why? ~5 Players near insert area with 32 FVD | *Test: Chunkli insert was super slow when testing fake-view distance? Why? ~5 Players near insert area with 32 FVD |
Latest revision as of 14:01, 4 November 2022
- FakeView Distance
- New structure for FakeChunks / Chunk Data / Packet data
- Bug: Fixed Viewdistance in mc commands (+1 in a lot of places)
- Datacomparison from vanilla chunks and fake chunks
- Create FakeChunks from Anti-XRay chunk data only
- Cleanup FakeviewDistance Codes, Move away from PlayerChunkMap
- Feature: Change implementation of commands to fully async
- Bukkit for some reason wants all commands to be sync by default. We do not want that!
- Test Chatterino
- Feature: /user playerrenderdistance
- Feature: /user entityrenderdistance
- Bug: RecentTPS is not updated correctly, check updateTicks in MinecraftServer
- Bug: Desktop slow if the Minecraft-Server is slow? Why?
- Test with a lot of hoppers running in the background
- Test: Chunkli insert was super slow when testing fake-view distance? Why? ~5 Players near insert area with 32 FVD
- Dynmap installed again & updated
- Render all worlds
- Update configs to be the same for all worlds
- Chunkli: Change the implementation of ForceCopyArea to allow very large areas to be copies and not cause a memory exception
- Use ~ 32*32 chunk sizes