Data adjustment suggestion: Hydra Orochi system

[khionu]

It'd be nice if we could represent the Orochi choice as a system. This seems like the easiest choice at first thought?

[msprijatelj]

The OROCHI Drones are already embedded into the Hydra’s CompCon data, and Active Mode can already track your active drones and deployables. I just now was able to deploy a new OROCHI Drone in Active Mode, and use that to represent the Hydra’s choice of drone.

Is this acceptable? If not, I’m uncertain what this feature will actually provide? Could you please elaborate with the following:

• Is this feature related to a problem? If so, what problem would this feature aim to resolve?
• What is the proposed implementation of this feature, in detail?
• Are there any acceptable alternative implementations you can think of?

[khionu]

This isn't quite helpful for me because I use Foundry as my main mode of play, and picking a drone is supposed to be done between scenes. RAW, you're supposed to pick one on creation. Even if I were using CompCon's Active Mode (which the Foundry module doesn't seem to sync with), this implementation allows someone to pick the drone they want after combat has started, and doesn't seem to restrict the player to the same drone. It even lets you deploy two different OROCHI

[msprijatelj]

If the issue is with Foundry, it’s more appropriate to make a Feature Request on the foundryvtt-lancer GitHub repo instead. The data is clearly available and usable, as shown by CompCon using it in Active Mode, so the Foundry system should be able to detect the deployables on its own to implement this, too.

[khionu]

To rephrase the new issue I'm seeing, according to RAW, you're supposed to pick your OROCHI when you create your mech, and it's not supposed to be changeable during combat. The current implementation doesn't allow you to set which is picked. Setting it at deploy time is too late.

[msprijatelj]

RAW, you can change OROCHI drones on a rest or full repair. See the last paragraph of OROCHI Drones. The current Active Mode implementation lets a pilot deploy any drone since it can change so easily. Plus if the pilot uses Full Deployment, they would want to be able to deploy all drones simultaneously.

I would anticipate trying to restrict the drones deployed would be a highly specific piece of code just for the Hydra that:

1. Would make it harder for users to flexibly change and deploy their OROCHI drones in active mode
2. Could be handled by just noting the chosen drone separately and deploying it as soon as combat begins

Because of this, I’m not convinced that implementing such a restriction is a net benefit for CompCon users.