SL21W27: Difference between revisions

From ETM
Jump to navigation Jump to search
No edit summary
No edit summary
Line 9: Line 9:
**Fix mc always loading world-spawn on player connection
**Fix mc always loading world-spawn on player connection
*'''Implement a DenyList to disable a set of blocks we do not want to be using in the beginning'''
*'''Implement a DenyList to disable a set of blocks we do not want to be using in the beginning'''
**Bundle
**'''Bundle'''
**ShulkerBoxes
**'''ShulkerBoxes'''
**Sculk sensor
**'''Sculk sensor'''
**Maps
**'''Maps'''
**ItemFrame / Paintings ? (should be ok because of special manager)
**ItemFrame / Paintings ? (should be ok because of special manager)
**Heads? (should be ok because of whitelist)
**Heads? (should be ok because of whitelist)
**Written Books? Probably want a management-system for this? Maybe like ISBN?
**'''Written Books? Probably want a management-system for this? Maybe like ISBN?'''
***We dont really need "random books" all over the place.
***'''We dont really need "random books" all over the place.'''
***Would even prevent all kinds of book-spam-attacks
***'''Would even prevent all kinds of book-spam-attacks'''
*'''Reimplement World-Saver and test validity by crashing the server after a save-execution'''
**'''Validate files are closed / reopened as expected'''
**'''Validate saving frequency is down a LOT as we save entities in their own system'''
**'''Validate entities are force-saved as well!'''
**

Revision as of 18:05, 9 July 2021

◄ SL21W26 | SL21W28 ►


  • 1.17.1 Update
    • EntityDestroyPacket accepts a list again \o/
    • Implement Entity copy in Chunkli with new EntityManagement-System of Minecraft
    • Implement stacking of chunk data test command
    • Fix mc always loading world-spawn on player connection
  • Implement a DenyList to disable a set of blocks we do not want to be using in the beginning
    • Bundle
    • ShulkerBoxes
    • Sculk sensor
    • Maps
    • ItemFrame / Paintings ? (should be ok because of special manager)
    • Heads? (should be ok because of whitelist)
    • Written Books? Probably want a management-system for this? Maybe like ISBN?
      • We dont really need "random books" all over the place.
      • Would even prevent all kinds of book-spam-attacks
  • Reimplement World-Saver and test validity by crashing the server after a save-execution
    • Validate files are closed / reopened as expected
    • Validate saving frequency is down a LOT as we save entities in their own system
    • Validate entities are force-saved as well!