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

[DECOHack] Auto Weapons #51

Open
MTrop opened this issue Sep 21, 2021 · 1 comment
Open

[DECOHack] Auto Weapons #51

MTrop opened this issue Sep 21, 2021 · 1 comment
Labels
enhancement Nice-to-haves and things that can actually help current behavior. low priority Issues labeled this are lower priority than regular bugs - rarer issues with workarounds. on hold This issue/enhancement needs other stuff to happen, or is held up by another issue.

Comments

@MTrop
Copy link
Owner

MTrop commented Sep 21, 2021

This issue is a spinoff of obsolete issue: #31

Proposal: A set of clauses that work like freeing states, but for weapons.

weapon free <INTEGER>
weapons free <INTEGER> to <INTEGER>

A weapon is filled/"un-freed" when it is directly edited, or filled in via the following:

auto weapon <IDENTIFIER> [ ":" ( auto weapon <IDENTIFIER> | weapon <INTEGER>) ] [<STRING>]
{
    // ..... code
}

For example:

auto weapon bfg10k : thing MTF_BFG "Ultra BFG 10k"
{
    // ... stuff ...
}

Now, of course, you will not know exactly which index it will end up in, so how will you refer to weapons later when you need to reference a specific weapon or its states? These clauses:

auto weapon bfg10k
auto weapon bfg10k refire

"Auto" objects will need to have a registrar in the context that will allow them to be referred to later, and so that namespace needs to be special when locating where those sorts of objects end up. Identifiers are better here, since using integers would be confusing, as that should be for specific slots, and this also keeps declaration and references lingustically distinct.

@MTrop MTrop added enhancement Nice-to-haves and things that can actually help current behavior. on hold This issue/enhancement needs other stuff to happen, or is held up by another issue. labels Sep 21, 2021
@MTrop
Copy link
Owner Author

MTrop commented Jul 22, 2022

I'm starting to think that this issue is a bad idea until a supporting port can re-allocate weapon slots - auto-filling can lead to slotting inconsistency, which directly affects gameplay and mods.

@MTrop MTrop added the low priority Issues labeled this are lower priority than regular bugs - rarer issues with workarounds. label Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Nice-to-haves and things that can actually help current behavior. low priority Issues labeled this are lower priority than regular bugs - rarer issues with workarounds. on hold This issue/enhancement needs other stuff to happen, or is held up by another issue.
Projects
None yet
Development

No branches or pull requests

1 participant