Use LeafPile and correct threading - #63

Merged

Cubicake merged 21 commits into

mainfrom

Jul 4, 2026

Commits on Jun 28, 2026

Include ParallelepipedLeafPile
Cubicake
committed
7dd2d20
Update leafpile and include it in PE module
Cubicake
committed
d5a55ef
Use SWMR and MTQueue
Cubicake
committed
de3ddd8
Add thread guards for netty thread
Cubicake
committed
b4e65f9
Mark fields volatile
Cubicake
committed
bdf2211
Remove unused import
Cubicake
committed
563f19e
Don't handle PlayerData lifecycle from main thread
Cubicake
committed
26ce1ff
Make self entity fields final
Cubicake
committed
d3a2b43
Move player registration to play phase only and handle disconnect from netty
Cubicake
committed
ea36d63
Skip already visible entities to prevent duplicate packets
Cubicake
committed
d66bf18
Create NettyData inside PlayerData, and just mark PlayerData as disconnected so that engine threads ticking the object don't break
Cubicake
committed
e963a69
Bump minimum supported version and use PlayerClientLoadedWorldEvent as it is after the play-phase join packet. This also requires guarding for null world in engine
Cubicake
committed
8afb1d1
Don't do unnecessary lookups
Cubicake
committed
d35adc6
Don't do unnecessary lookups
Cubicake
committed
331310d
Remove unused import
Cubicake
committed
344f259
Move null state guard here
Cubicake
committed
b554000
Turns out ConcurrentHashMap is better; Also entityUUIDsByID is accessed from netty thread only so it can be a fastutil map
Cubicake
committed
02253fd
Bump version
Cubicake
committed
ce8ce72

Commits on Jun 29, 2026

Use SWMRHashTable for lock-free work
Cubicake
committed
f7d21a7

Commits on Jul 1, 2026

Make sure test can't be JIT optimised away
Cubicake
committed
50b259e

Commits on Jul 3, 2026

Bump version
Cubicake
committed
c814e1e