- Joined
- Apr 25, 2017
- Messages
- 3,259
- Nebulae
- 4,337
Suggestion: Codify a method that allows player-controlled manhacks to be utilized on the server in a way that doesn't require direct staff oversight.
Assuming we can utilize the AirWatch 2.0 addon (or whatever it was called). I don't know how Lua code works and what limits are so what I write is likely easier said than done but currently, I can imagine something like this:
Add a new 'Enhanced Viscerator' class based on the current naming convention: AW:ENHC.VSCR-XXX
Add a new script, Enhanced Viscerator, or alternatively, add a command /deploymanhack that requires a manhack script in inventory to work
When this script or command is used, it creates a 'request'. This request could be constantly active, moving with the deploying player, it could be active but remain at the point it was used or it requires the player to remain standing still.
Then, the manhack player can do a command or some other way to find this 'request' and deploy at that request in the player manhack form.
Then, to recall at the command of either the deploying unit or for some other reason, the player manhack can do a command /recall or something akin to it and it would simply drop the script again at it's current location.
Finally, if this player controlled manhack (assuming we utilize the variant from AirWatch 2.0) can have it's damage values adjusted with similair attacks, I'd encourage for the undeployed blades to do 1 or no damage and when deployed blades do 10-15. Significant enough in theory to be a threat but not enough to be dominating.
Why it would be worth adding:
- Provides more gameplay
- Provides more opportunity to utilize a deployable that too often relied/relies on wonky AI
- Allows manhacks to be used in a S2RP capacity at times
- Additionally, it would provide an interesting avenue for RP if we go by the patient zero video
Necessary content: Gary's will to try and code something based on a loose explanation.
Assuming we can utilize the AirWatch 2.0 addon (or whatever it was called). I don't know how Lua code works and what limits are so what I write is likely easier said than done but currently, I can imagine something like this:
Add a new 'Enhanced Viscerator' class based on the current naming convention: AW:ENHC.VSCR-XXX
Add a new script, Enhanced Viscerator, or alternatively, add a command /deploymanhack that requires a manhack script in inventory to work
When this script or command is used, it creates a 'request'. This request could be constantly active, moving with the deploying player, it could be active but remain at the point it was used or it requires the player to remain standing still.
Then, the manhack player can do a command or some other way to find this 'request' and deploy at that request in the player manhack form.
Then, to recall at the command of either the deploying unit or for some other reason, the player manhack can do a command /recall or something akin to it and it would simply drop the script again at it's current location.
Finally, if this player controlled manhack (assuming we utilize the variant from AirWatch 2.0) can have it's damage values adjusted with similair attacks, I'd encourage for the undeployed blades to do 1 or no damage and when deployed blades do 10-15. Significant enough in theory to be a threat but not enough to be dominating.
Why it would be worth adding:
- Provides more gameplay
- Provides more opportunity to utilize a deployable that too often relied/relies on wonky AI
- Allows manhacks to be used in a S2RP capacity at times
- Additionally, it would provide an interesting avenue for RP if we go by the patient zero video
Necessary content: Gary's will to try and code something based on a loose explanation.
Last edited:
Reactions:
List
