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

feat(garage): resolve virtual garage spawns by lane and selected session vehicle #11

Merged
J.Schmidt92 merged 4 commits from docus into master 2026-04-22 17:59:41 -05:00
Conversation 0 Commits 4 Files Changed 317 +46482 -82
J.Schmidt92 commented 2026-04-22 17:59:33 -05:00
Owner
Copy Link

Summary

This updates the garage client flow so virtual garage spawning uses the active garage context and category spawn lane, and only finalizes the vehicle selected in the current BIS virtual garage session.

It also updates the garage docs to match the implemented behavior.

Problem

Virtual garage close handling was scanning for nearby vehicles around the preview center and could pick up an unrelated world vehicle instead of the vehicle selected in the virtual garage.

That caused cases where selecting an ATV/quad would grab a different nearby vehicle, move it, and respawn it.

Changes

  • resolve the active garage interaction context instead of relying on mission-configured location iteration
  • resolve category-specific spawn lanes from nearby garage* markers
  • block virtual garage access when the resolved spawn position has a vehicle within 5 meters
  • finalize only the vehicle created during the active BIS virtual garage session
  • prevent unrelated nearby world vehicles from being treated as virtual garage spawn candidates
  • clear temporary virtual garage session state after close
  • document the spawn lane and spawn blocking behavior

Files

  • arma/client/addons/garage/functions/fnc_openVG.sqf
  • arma/client/addons/garage/functions/fnc_initContextService.sqf
  • arma/client/addons/garage/functions/fnc_initHelperService.sqf
  • arma/client/addons/garage/functions/fnc_initActionService.sqf
  • arma/server/addons/garage/functions/fnc_initGarage.sqf
  • arma/client/addons/garage/README.md
  • docs/CLIENT_GARAGE_USAGE_GUIDE.md
  • docus/content/4.client-addons/6.garage.md

Testing

Manual in-game validation:

  • opened the virtual garage at a garage with lane markers
  • left another vehicle parked near the area
  • selected and spawned the ATV/quad from virtual garage
  • confirmed the selected vehicle spawned correctly
  • confirmed the unrelated nearby vehicle was not moved, deleted, or respawned

Notes

Nearby world vehicles are only used for the virtual garage spawn blocking check at the resolved lane. They are not eligible spawn candidates.

## Summary This updates the garage client flow so virtual garage spawning uses the active garage context and category spawn lane, and only finalizes the vehicle selected in the current BIS virtual garage session. It also updates the garage docs to match the implemented behavior. ## Problem Virtual garage close handling was scanning for nearby vehicles around the preview center and could pick up an unrelated world vehicle instead of the vehicle selected in the virtual garage. That caused cases where selecting an ATV/quad would grab a different nearby vehicle, move it, and respawn it. ## Changes - resolve the active garage interaction context instead of relying on mission-configured location iteration - resolve category-specific spawn lanes from nearby `garage*` markers - block virtual garage access when the resolved spawn position has a vehicle within 5 meters - finalize only the vehicle created during the active BIS virtual garage session - prevent unrelated nearby world vehicles from being treated as virtual garage spawn candidates - clear temporary virtual garage session state after close - document the spawn lane and spawn blocking behavior ## Files - `arma/client/addons/garage/functions/fnc_openVG.sqf` - `arma/client/addons/garage/functions/fnc_initContextService.sqf` - `arma/client/addons/garage/functions/fnc_initHelperService.sqf` - `arma/client/addons/garage/functions/fnc_initActionService.sqf` - `arma/server/addons/garage/functions/fnc_initGarage.sqf` - `arma/client/addons/garage/README.md` - `docs/CLIENT_GARAGE_USAGE_GUIDE.md` - `docus/content/4.client-addons/6.garage.md` ## Testing Manual in-game validation: - opened the virtual garage at a garage with lane markers - left another vehicle parked near the area - selected and spawned the ATV/quad from virtual garage - confirmed the selected vehicle spawned correctly - confirmed the unrelated nearby vehicle was not moved, deleted, or respawned ## Notes Nearby world vehicles are only used for the virtual garage spawn blocking check at the resolved lane. They are not eligible spawn candidates.
J.Schmidt92 added 4 commits 2026-04-22 17:59:34 -05:00 
- Created package.json for Docus with necessary scripts and dependencies.
- Implemented sync-docus-docs.mjs to automate the generation of documentation files from source markdown.
- Defined mappings for generated pages and virtual routes to ensure proper linking in documentation.
- Added static content files for the documentation structure, including navigation and index pages.
J.Schmidt92 merged commit 461b75443b into master 2026-04-22 17:59:41 -05:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
J.Schmidt92
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: IDSolutions/forge#11
No description provided.
Delete Branch "docus"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?