-
-
Notifications
You must be signed in to change notification settings - Fork 0
Reference API surface and stability
Which packages are public, what stability each carries, and which types are annotated
@ApiStatus.Experimental.
This page is a generation target, currently written by hand. Source of truth: the
@ApiStatusannotations on the public types of the Falco repository. The per-type list below is what a generator would replace first.
| Package | Module | Stability | Binary-compatibility baseline |
|---|---|---|---|
net.onelitefeather.falco.anvil |
falco-anvil |
experimental — all 24 public types annotated | checked against the last release |
net.onelitefeather.falco.light |
falco-light |
experimental — all public types annotated | checked against the last release |
net.onelitefeather.falco.instance |
falco-instance |
see the module Javadoc | checked against the last release |
net.onelitefeather.falco.migration |
falco-migration |
experimental — all public types annotated | excluded — not yet released |
Experimental means: signatures, class layout and behaviour may change in a minor release. Do not rely on these types in code you cannot adapt.
ChunkMigrationMode and ChunkMigrator live in net.onelitefeather.falco.anvil but belong to the
migration feature, and carry the same experimental annotation.
FalcoAnvilLoader,
RegionFile,
RegionConstants,
ChunkCompression,
BitPacker,
PaletteData,
PaletteEntryResolver,
BlockPaletteResolver,
BiomePaletteResolver,
NbtReads,
SectionCodec,
AnvilDiagnostics,
AnvilChunkException,
AnvilFault,
AnvilFormatException,
ChunkDataException,
ChunkLocation,
RegionFormatException,
ChunkVersionPolicy,
DefaultChunkVersionPolicy,
UnknownEntryPolicy,
DefaultUnknownEntryPolicy,
ChunkMigrationMode and
ChunkMigrator.
(The package-private SectorAllocator and ServiceResolution carry no annotation and are not among
the twenty-four.)
Nothing switches to a Falco type by itself. A server keeps using whatever loader, light path and
instance it uses today until it constructs the Falco equivalent explicitly. A migration engine on
the classpath migrates nothing until a caller selects a ChunkMigrationMode.
Related: Reference Modules and coordinates · Reference Supported versions ·
Build Setup for what checkApiCompatibility does
Every published table lives on Reference Measured results, which owns them; a correction is made
there and nowhere else. What the ± after a JMH mean covers is defined once, in
Explanation What a measurement here means.
Wiki home · Repository · README and quick start · API documentation · Issues · Licence: AGPL-3.0
Getting started
How-to guides
- How-to Add Falco to your build
- How-to Load an Anvil world
- How-to Compute light for a loaded world
- How-to Keep chunk light up to date automatically
- How-to Use FalcoInstance instead of InstanceContainer
- How-to Migrate a world from an older version
four more
Reference
six more
Background
- Explanation Choosing between Falco and the built-in loader
- Explanation Scope and non-goals
- Explanation When light computation actually runs
- Explanation What a measurement here means
nine more
- Explanation Choosing between FalcoInstance and InstanceContainer
- Explanation How the Anvil loader is built
- Explanation How the light engine works
- Explanation How the concurrency design works
- Explanation How world migration works
- Explanation The chunk version guard
- Explanation Why a second Anvil loader
- Explanation Why a custom light engine
- Explanation Why falco-instance exists
- Explanation Comparing the light engine with Minestoms
- Explanation What the benchmarks establish
Project record
Working on Falco