Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEATURE: Restricted weapons #1

Open
thebgpikester opened this issue Jul 19, 2019 · 1 comment
Open

FEATURE: Restricted weapons #1

thebgpikester opened this issue Jul 19, 2019 · 1 comment

Comments

@thebgpikester
Copy link

We can (already) remove and re-add, on landing and takeoff, weapons to a fixed table containing the total inventory to store online. We have a PoC working with this to the back end server. Fuel is possible and optional (and imo, pointless in the Gulf) It can still be recorded though for data purposes.

The gameplay for this is to force restrictive loadouts to players, and avoid, "Best in slot" weaponry by limiting them which introduces choices and variety.

The "limiting" is not a hard limit of prevention in game. It's based on the planning cycle where the warehouse is visible to all pilots and they must agree together on usage.

Currently the working theory is that players will see the weapon limits available in a planning section, make choices and adhere to them. The actual weaponry returned for reuse is recorded throughout the mission and the warehouse updates for the next planning cycle. It could be changed at any time by administrator.

http://client.tnc.today/api/v1/warehouse/1/jp5

I think the only part really requiring work is the visual design/presentation part of the ATO work.

@132ndNeck
Copy link
Collaborator

This should be tied into Issue #5 the ATO in a way, especially the visual design/presentation part

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants