Say that Minestom's chunk events still fire, and when to take which
The usage page introduced ChunkLifecycleListener without mentioning that
InstanceChunkLoadEvent, InstanceChunkUnloadEvent and PlayerBlockBreakEvent are
dispatched by FalcoInstance exactly as they are by a container. Read as written,
it suggested the listener is how you observe a chunk here, which would push
application code onto an interface that runs inside the chunk lock and whose
throws fail a load. The events are the right default; the listener is for acting
before anybody else sees the chunk, and for per-block notification.
Add a usage page for falco-instance, which had none
The wiki had a usage page for each of the other two modules -- Anvil Chunk
Loader and Light Engine -- and for the instance it pointed at Rationale:
Instances and Chunks instead. That page answers why the module exists and what
it refuses to do; it never showed anybody how to use it. The sidebar entry said
as much by naming the rationale page "the third module".
Instances and Chunks is that missing page: when it is worth taking, the builder,
the chunk loader form, the combination with the light engine that only became
possible in 1.0.0, both lifecycle routes, shared worlds, and the accessors that
read a lazy chunk without materialising it -- getSections() allocates all 24
sections, which is the one thing on this module that is easy to trip over.
Every code block is compiled rather than typed into a page. WikiSnippetCheck in
falco-demo carries all of them, and writing it found an error before a reader
could: the light engine block said new ChunkLightScheduler(instance), and the
constructor takes a ChunkLightService.
Navigation updated in the three places a new page needs it -- the sidebar, the
Using Falco list on Home, and the rationale page, which now points forward to
the usage page as well as being pointed at.