Ashfall 1.0.1

Ashfall 1.0.1 — Terminal “Turn In” Button Dispatch Fix

@everyone

This Ashfall 1.0.1 fix targets a specific ScreenCore Terminal bug where the Survival Route mission button could show the correct action, such as Turn In, but fail to send the mission completion action through the correct server route.

The issue was likely caused by the button resolving the right mission action locally, then dispatching it through a stale or non-mission tab such as:

echoterminal:overview

When that happened, the server had no mission handler for the packet, causing the action to fail or produce an unknown Terminal action signal.

Fixed

Survival Route “Turn In” Button

The ScreenCore Survival Route Turn In button now reliably sends the selected mission’s completion action to the server.

Mission actions from the Survival Route now dispatch through the correct mission route tab:

echoterminal:main_survival_route

This applies even when the ScreenCore data context has a missing, stale, or Overview-normalized active tab.

Improved

Mission Action Routing

Terminal ScreenCore mission actions now separate:

• the page/tab currently displayed in the UI
• the server action routing tab used for mission packets

This prevents mission buttons from accidentally using the wrong active tab when sending actions to the server.

Routing behavior now follows the correct mission context:

• Survival Route mission actions use echoterminal:main_survival_route
• Vanilla Journey mission actions use echoterminal:vanilla_journey
• Overview or stale active tab values are ignored for mission action packets

Refactored

Mission action sending is now handled through one shared helper used by:

• Complete
• Claim Rewards
• Track
• Contextual Turn In

The shared dispatch path now:

• keeps action-value as the selected mission id fallback
• preserves the requested action_id when present
• sends the exact resolved action when activate_selected_mission finds a valid primary action
• avoids recomputing or replacing the resolved mission action unnecessarily
• uses a robust route-tab fallback instead of trusting stale UI tab state

Server Behavior

MissionCore handling remains server-side through the existing Survival Route delegation.

This fix does not change:

• mission completion rules
• reward claim semantics
• MissionCore progression logic
• the five-button action strip layout
• legacy renderer behavior

The Survival Route remains the aggregator and continues delegating MissionCore actions through MainSurvivalQuestProvider.

Test Coverage

Added or updated Terminal test coverage for:

• activate_selected_mission routing complete through MainSurvivalQuestProvider.TAB_ID
• missing active tab fallback behavior
• stale overview active tab fallback behavior
• perform_mission_action honoring explicit action_id
• rejection of unavailable action ids
• Survival Route delegation of MissionCore complete
• Track and Clear Tracking using the same robust route-tab fallback

Build Validation

Recommended compile checks:

gradlew.bat :echoterminal:compileJava
gradlew.bat :echomissioncore:compileJava
gradlew.bat compileJava

Manual QA

Tested target flow:

1. Open the remote Terminal on a server.
2. Open the Survival Route.
3. Select Craft Scrap Knife when the requirement shows 1/1.
4. Click Turn In.

Expected result:

• The mission changes from READY to completed or claimable state.
• The Terminal updates without needing to reopen it.
• No “Terminal action signal unknown” message appears.

Also verify from the same mission panel:

• Complete still works
• Claim Rewards still works
• Track still works
• Contextual Turn In keeps the correct label when MissionCore exposes complete as Turn In

Notes

This is a dispatch reliability fix, not a layout redesign. The existing five-button mission action strip stays in place.

Ashfall 1.0.1 continues tightening the Terminal experience so mission actions feel instant, reliable, and server-safe.

Ashfall 1.0.0

Ashfall is now ready for public beta testing through ECHO Launcher.

This release uses the new strict ECHO pack format, which means the launcher verifies release metadata, the pack manifest, and the compressed pack archive before installing. Testers should use ECHO Launcher and the Play Ashfall button. Minecraft account login and final launch are handled by the official Minecraft Launcher.

What’s Included

• Official Ashfall beta modpack
• Minecraft Launcher handoff support
• SHA-256 verified pack install
• Automatic install, repair, and verification flow
• Safe modpack export format with embedded ECHO metadata
• Saves, logs, screenshots, auth files, cache, and private runtime files excluded from the pack archive

Required Release Assets

This release must include these three files:

• echo-release.json
• ashfall-stable-1.2.0-beta.1.pack.json
• Ashfall-1.2.0-beta.1.echo-pack.zip

Important Beta Notes

Back up your worlds before testing. Ashfall includes world generation content, so existing worlds may behave differently after pack updates.

Do not install from a bare zip. ECHO Launcher requires the strict release metadata so it can verify the pack before installing.

How To Play

1. Install or update ECHO Launcher.
2. Open ECHO Launcher.
3. Press Play Ashfall.
4. Let ECHO install and verify the pack.
5. Minecraft Launcher will open for Microsoft login and final play.

Status

Ashfall is the only playable beta pack right now. Orbtial is listed in the launcher as an upcoming official preview, but it is not playable yet.