AI Companion Fabric

0.2.9 — Unfinished builds, part 2: it remembers where

Bundles PlayerEngine 1.0.79. Self-contained jar as always — don't install a standalone engine alongside it.

Nothing to do after updating.

It can carry on with yesterday's house

0.2.8 stopped a returning build paying twice for the wall it had already put up. It still could not find that wall again: what the companion knew about a half-built structure lived in memory for ten minutes, and the things that interrupt a big build — quitting the world, a long gathering trip — outlast that. Asked afterwards to carry on, it had only the conversation to go on, so it guessed. In one measured case the half-built house was at (180, 62, -40) and its "continuation" was planned at (191, 64, -39): a second house, eleven blocks away, priced as very nearly a whole new building.

A build that stops short is now written to disk — the plan, the position, and how much of it is standing — while it runs, not only when it ends, since quitting and cancelling tear the task down without running any of its endings. There is no expiry; the record is cleared when the build finishes.

Picking up where I left off — 379 of 550 blocks were already up.

Its status carries that record too, so it knows the house exists without having to remember the conversation. Matching is by position rather than wording, so a rephrased request — or a typo — still finds it.

One unfinished build is remembered per companion, and ignored in another dimension, since a plan pins absolute coordinates.

0.2.8 — Voice switches itself on · Unfinished builds, part 1

Bundles PlayerEngine 1.0.74. Self-contained jar as always — don't install a standalone engine alongside it.

Nothing to do after updating. Voice is on by default now; an existing config saying "tts": {"enabled": false} stays off, so set it to true once if you want it.

Starting the container is the whole setup

Voice needed two steps: run the Kokoro container, then find the config file and enable it. The second is the one nobody got to — and on a dedicated server it meant shell access, since the settings screen edits your own machine's copy rather than the server's.

The setup now ships with the mod, unpacked to config/aicompanion/tts/ on first launch. The whole procedure:

cd config/aicompanion/tts
docker compose up -d

Companions speak as soon as it answers. No config edit, no restart.

It was waiting out speech that never happened

Voice was off by default for a reason: leaving it on made every companion slower.

The server could not know whether a line had actually been spoken — your machine fetches and plays the audio, and the server cannot see whether anything there is listening on the Kokoro port. So it guessed: a companion was treated as mid-sentence for roughly one second per 25 characters, and it will not start its next reply while it believes it is still talking. With no container running that was pure loss — five to nine seconds of silence per line, waiting out audio that never played.

Your machine now reports back, either "that line has finished" or "I have nowhere to play this", and that is what releases the companion. It waits exactly as long as it is really speaking, and a machine with no Kokoro server costs nothing: one refused connection, then it is left alone for five minutes. /companion reload retries immediately.

The container belongs on the player's machine, not the server's — http://localhost:8880 has to mean something where you are sitting. On a dedicated server, either each player runs their own or you point tts.endpoint at one everybody can reach.

A half-built house asked to be paid for twice

Interrupt a big build and ask for it again, and the companion refused — insisting on hundreds of planks it had already put into the walls. One case: a 13×15 house stopped at 287 of 550 blocks, then demanded 319 oak planks. Collecting them did not help, because the bill grew back to the full amount every time.

The affordability check ran before the companion had looked at the site, so it priced all 550 cells against an inventory that had spent a third of itself on the first 287. It now walks to the site and prices only what is genuinely left. A build holding enough for the remainder carries on; one that is really short says something true — "I've got 287 of 550 blocks up — I need 40 oak planks to finish it".

Finding that house again after a restart is 0.2.9.