Skip to content

Why is this a framework?

Seijax edited this page May 19, 2024 · 19 revisions

> To lower the barrier of entry to this tech

Adding this framework as a requirement to their mods, allows modders to refocus on the guns themselves instead of having to delve into redscript classes in order to set something like this up.

> To avoid the risks (and costs) of multiple implementations

Having multiple modders wrap and replace the same functions, in order to make their weapon mods completely standalone, would be a nightmare... and in all probability actually make them incompatible with each other.

> To micromanage past current technical limitations

Modders interested in realizing weapons that use these functionalities should pay special attention to two criticalities:

  • Sounds: because firing sounds can glitch when firing with a dramatically shorter cycletime than the one of their original gun (ie: turning a slowfiring semiauto gun into fullauto or burst)
  • StatModifiers: because some StatModifiers only apply to the secondary firemode, while others are dedicated to only apply while aiming (or not).

All of these things can be managed and worked around (ie: using the audioName of another gun, tweaking tweakdb values,...) but require interested modders to smooth the adaptation of existing weapons to this new functionalities.