Fluidlogged API Migration

Fluidlogged API Migration

简体中文 | English

If a world previously used Fluidlogged API, Farmer's Future Delight can read its stored fluid records as chunks load after Fluidlogged API is removed.

Records allowed by the current settings are converted automatically when the original block and fluid can still be identified. Records that need your decision can be handled through the dialog or /ffd_fluidmigration.

Back up your world and configuration first. Keep the other mods that provide the original blocks and fluids. This is a one-way import after removing Fluidlogged API, not two-way synchronization between two active fluidlogging systems.

Start with this command

/ffd_fluidmigration status

It lists block/fluid combinations awaiting a decision in currently loaded chunks, along with their commands and tokens. When run by a player in game, it also reopens one pending migration dialog if any are available.

Having no pending decisions does not mean the entire world has finished migrating. Areas that have not loaded yet are checked when they load later.

Who can use it?

• The single-player world owner, even with cheats disabled.
• Multiplayer administrators with command permission level 2.
• The server console with the appropriate permissions.

Ordinary multiplayer players cannot choose the server's migration policy.

What do the dialog options mean?

The English interface uses these button labels:

Button	Result
Convert + update config	Keep fluids that can be safely converted and adjust only the necessary block and fluid permissions
Discard contained fluid	Keep the blocks but remove the matching old fluid records; a second click confirms the choice
Later (retain data)	Leave the records untouched for now; use status to reopen the prompt later

Do not break, replace, or otherwise modify the affected blocks before deciding.

If the original block has changed or a mod providing the block or fluid is missing, conversion may be unavailable. Do not discard data just to get past the dialog: you can keep it pending while checking missing mods or restoring a backup.

Administrator and console commands

Run status first, then copy the current token from its output. A token identifies a pending request; it is not a coordinate, a block ID, or a name you choose yourself.

Keep fluids that can be converted:

/ffd_fluidmigration convert <token>

Remove the matching old fluid records:

/ffd_fluidmigration discard <token>

Warning: running discard directly submits the removal decision immediately. It has no second-click confirmation like the dialog. Do not reuse someone else's token or run it without understanding its scope.

Tokens apply to current pending requests and may expire after a restart or state change. If a token has expired, run status again rather than repeatedly retrying the old token.

What does my choice affect?

Keeping fluids

Conversion adjusts the required settings instead of allowing every block or fluid without restriction. For example, if one non-water fluid needs permission, only the necessary permissions are added.

Configuration is shared; it does not belong only to the current world. Other worlds using the same configuration are affected too. Server settings are not personal preferences for a single player.

Relevant loaded chunks are processed shortly afterward; other chunks are processed when they load. Records that can be identified and safely converted retain their fluid type and flow level. Flowing fluids are not all turned into source blocks.

Removing fluids

Removal decisions are recorded by the combination of host block registry ID + fluid block registry ID, not just for the single block in front of you.

Matching old records in the same world, including areas loaded later, follow that removal decision. The host blocks remain, and ordinary bodies of water around them are not the target of this cleanup.

This does not permanently forbid those blocks from containing fluids again. It handles the matching records imported from the old system. There is currently no dedicated command to undo a removal decision, so make a backup first.

Common questions

Situation	What to do
I closed the dialog and want to decide later	Run /ffd_fluidmigration status
No decisions are pending	Currently loaded chunks have no pending requests; other areas may not have loaded yet
I cannot convert the fluids	Check for changed blocks or missing mods; keep the records pending while investigating
Configuration could not be saved	Check whether the configuration files are read-only and whether the game/server has write permission; old records are retained
Old data cannot be recognized	It is preserved unchanged rather than silently discarded; check the game log
Fluidlogged API is still installed	This migration does not run while it is present; complete the mod switch using your backup plan first

---

Back to Command Overview