Implemented my idea in !1497, this thread can be resolved.
It's not that I don't like the idea, it's that doing so is feature creep and would be best deferred until after this change is in place. The Overki...
It doesn't look good to me, my idea was to allow having unique aliases for all weapons, you removed all the weapon_ok* aliases and added the ball s...
Alright, I've made that change.
Indeed, that would the ideal outcome, as noted previously:...
-
64baf870 · Give the weapon impulse field a unique name to avoid some confusion
- ... and 98 more commits. Compare cedebabe...64baf870
Done....
Since Overkill weapons aren't mean to be used together with the normal weapons, what about giving okmachinegun, oknex and okshotgun the same .m_uni...
To remove ambiguity with .impulse I suggest renaming .m_impulse to .m_unique_impulse.
Given the thread was resolved I'm going to assume the Ball Stealer/Overkill issue is not a roadblock. A TODO note is in place so that it doesn't ge...
Has a consensus been reached that this is a rejected approach to solving the problem? If so, please advise so that it can be closed.
Recently I discovered that every networked entity and every cached sound/model needs to be sent to the client while connecting, and with enough sou...