IDSolutions/forge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refine transport service documentation for clarity and conciseness

Browse Source
This commit is contained in:
Jacob Schmidt 2026-05-25 15:31:43 -05:00
parent bda6359e7c
commit 1454a29de9
2 changed files with 2 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/MISSION_DESIGNER_GUIDE.md
View File

@ -150,8 +150,7 @@ Minimum Eden setup:
Transport nodes are generic paid travel points. They can represent ferries,
airports, bus stops, teleport terminals, or any other mission transport system.
The framework owns the menu, billing, cargo scan, and movement logic. The
mission only needs placed objects and arrival markers.
The framework owns the menu, billing, cargo scan, and movement logic.
![Eden transport location one](images/eden/transport_loc_1.jpg)

8
docs/TRANSPORT_SERVICE_GUIDE.md
View File

@ -2,7 +2,7 @@
The transport service provides paid point-to-point travel for players and
nearby vehicles or passengers. It is framework-owned: missions only need placed
transport objects and optional arrival markers with the expected variable names.
transport objects and arrival markers with the expected variable names.
## Mission Contract
@ -135,9 +135,3 @@ These screenshots show the default transport setup and player workflow:
![Player transport destination submenu](images/player/transport_destination_menu.jpg)
![Player transport completion notification](images/player/transport_complete.jpg)
## Mission-Side Code Requirement
No mission-side transport service, addAction script, or server event bridge is
required. The framework handles menu discovery, destination selection, pricing,
billing, cargo movement, and EventBus notifications.