Checking player status…
View all
Browse Afterfall articles
reference / Afterfall

Integration API and multiplayer limits

Read the exact scope of API v1, ComputerApps and persistent state before claiming an add-on or combined server works.

Afterfall 0.14.0Java 1.21.1NeoForge

Optional hooks

AfterfallIntegration API version 1 and ComputerApps are reported in 0.14.0. No registrations preserves base behavior. Civic Frontier is optional, not a base dependency. A hook’s existence does not prove its installed add-on registers it or that the exact pair was runtime-tested.

HookContract and boundary
ClaimProviderRequired claimants must allow an action. A provider may replace Afterfall player-team claim decisions while teams, stockpiles and NPC community records remain stored.
registerNoMaterializeVetoes candidate physical-infected materialization positions; does not repel infected already walking, migration or hordes.
registerNeedsPausedHolds/neutralizes survival drain, courses and damage under the contract; eating, drinking, sleep/healing and wound recovery remain available. At most once/player/server tick caching.
registerGridVetoVetoes mains per chunk column, with cached answers and add-on invalidation. Independent generators, batteries and reactor lines remain valid.
ComputerAppsRegisters buttons/openers for usable powered computers; add-ons must recheck later usability as appropriate.

API v1 does not establish money-to-fuel upkeep payments or custom third-party radio channels. Those belong to later requested work, including API v2 proposals.

Cross-mod interpretation

Afterfall’s claims, teams, NPC communities, supply tokens and jobs remain distinct from Civic Frontier’s civic systems. No pack configuration or exact add-on binary has been supplied for verification in this wiki task. Proposed cross-links are left in the section handoff for the main chat to verify; this section does not rewrite another mod’s integration documentation.

The report lists real add-on integration, other-player grime rendering, slim-arm alignment and some client/escort/media paths as untested. The author’s historical 829-GameTest claim is not a combined-mod multiplayer certification or a test run performed here.

Admin & server owner reference

Exact identifiers, original fields and source locators are preserved below. These records describe the documented mod version; they are not commands to run or proof of a new gameplay test.

State ownership

Survivor attachments hold needs, wounds, infection, skills, vice state and skin grime, with compact visual synchronization. World/community data holds plans, ledgers, NPC jobs, claims, utilities and environmental scenes. Campaign/account ledgers hold party objectives/choices, contributions, pending/paid rewards, endings and death history. Block entities/item data hold machines, water/fuel/energy, breakers, towers, board text, vehicles and clothing/sponge state.

These are designed synchronization/persistence paths. Network messages and save fields do not substitute for a two-client/restart test.

Sources & verification

Evidence: pdf-derived. Feature status: mixed. Article coverage: ready.

Afterfall_0.14.0_Extensive_Mod_Breakdown.pdf

PDF pages 3, 38, 70, 209–210 · 01 Dependencies; 14 Apps; 23 Integration API; 31 Limits · Afterfall 0.14.0 report: E002–E006, E097, E149–E154, E184–E186

Reported static findings and packaged-guide behavior. Underlying source/JAR and gameplay have not been rechecked for this wiki; pack overrides are unknown.

The wiki has not independently playtested report-derived instructions. Your server or modpack settings may change them.

Editor setupEditing guide →