Skip to content

Add tessera-api extension module for third-party block-data access - #61

Merged
InventivetalentDev merged 1 commit into
mainfrom
claude/tessera-block-data-api-u5xn7a
Jun 15, 2026
Merged

InventivetalentDev merged 1 commit into
mainfrom
claude/tessera-block-data-api-u5xn7a

Conversation

@InventivetalentDev

Copy link
Copy Markdown
Owner

Expose a stable, read-only extension API so other plugins can reuse Tessera's pre-baked block data (per-chunk MineSkin head textures) without bundling any of it themselves.

  • New tessera-api Gradle subproject: interface-only artifact (TesseraApi, SkinPayload, ChunkLayout, BakeOutcome, Tessera accessor, TesseraBlockBakedEvent). The shared value types (BlockKey, BakeKey, ChunkCoord) move into it under the same package, so plugin code is unchanged. Shadow leaves org.inventivetalent.* unrelocated, so the api ships in the plugin jar and resolves through Tessera's classloader at runtime (Vault/WorldEdit pattern). Publishable via maven-publish.
  • TesseraApiImpl: read-only facade registered with Bukkit's ServicesManager, backed by HeadsRegistry (queries), FakeBlockFactory.layout (pre-oriented per-chunk data) and BlockBaker (on-demand requestBake). Licensing is invisible to consumers — baking is the baseline; NOT_CONFIGURED only when the server has neither a MineSkin key nor a license.
  • FakeBlockFactory.layout reuses the same BlockGeometry math and a single canonicalRotation() helper as the spawn path, so consumers get pixel-identical placement and the face-rotation invariant stays in one place.
  • BlockBaker.onBaked hook fires TesseraBlockBakedEvent on the main thread after a successful runtime bake.
  • Consumer quickstart in docs/api.md; architecture note in CLAUDE.md.

Expose a stable, read-only extension API so other plugins can reuse Tessera's
pre-baked block data (per-chunk MineSkin head textures) without bundling any of
it themselves — e.g. block-placing/decoration plugins.

- New `tessera-api` Gradle subproject: interface-only artifact (TesseraApi,
  SkinPayload, ChunkLayout, BakeOutcome, Tessera accessor, TesseraBlockBakedEvent).
  The shared value types (BlockKey, BakeKey, ChunkCoord) move into it under the
  same package, so plugin code is unchanged. Shadow leaves org.inventivetalent.*
  unrelocated, so the api ships in the plugin jar and resolves through Tessera's
  classloader at runtime (Vault/WorldEdit pattern). Publishable via maven-publish.
- TesseraApiImpl: read-only facade registered with Bukkit's ServicesManager,
  backed by HeadsRegistry (queries), FakeBlockFactory.layout (pre-oriented
  per-chunk data) and BlockBaker (on-demand requestBake). Licensing is invisible
  to consumers — baking is the baseline; NOT_CONFIGURED only when the server has
  neither a MineSkin key nor a license.
- FakeBlockFactory.layout reuses the same BlockGeometry math and a single
  canonicalRotation() helper as the spawn path, so consumers get pixel-identical
  placement and the face-rotation invariant stays in one place.
- BlockBaker.onBaked hook fires TesseraBlockBakedEvent on the main thread after
  a successful runtime bake.
- Consumer quickstart in docs/api.md; architecture note in CLAUDE.md.

https://claude.ai/code/session_01PCARQEjpqBNzZTD7mHC7VB
@InventivetalentDev
InventivetalentDev merged commit d5e22c5 into main Jun 15, 2026
1 check passed
@InventivetalentDev
InventivetalentDev deleted the claude/tessera-block-data-api-u5xn7a branch June 15, 2026 10:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants