You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
several addons frequently do something foolhearty like doing a timer.Create and losing track of the things they were meant to apply or being interrupted by a round lifecycle event like a round ending -- or more likely not being interrupted when they should be.
some examples:
literally everything the mario mushroom does, it could not possibly be more wrong
eagleflight / tasers will restore a "bad" copy of your inventory and statuses (if at all) if the game as a short post-round pre-round
entity bound things are frequently given timers that make it so only one can possibly exist at a time due to Works On My Machine™ network conditions
Describe the solution you'd like
the fundamental problem has two main components:
people lack the foresight to bind things to EntIndex()
people frequently use timers to "undo" shit that they are about to "do"
destroy and apply the undo operations prior to TTTPostRound or when transitioning to any phase other than the current one
migrate as much code as is appropriate to use these APIs and include using these types of things as examples of "porting" an addon to TTT2
I didn't include all the timer arguments here for brevity but the idea is apparent: create a superset of that API more tightly coupled to the lifecycle of entities via extending the EntityMeta or whatever. Special handling may be warranted by making the implementation for PlayerMeta different.
Describe alternatives you've considered
there is no way to stop people from making chatgpt-tier addons
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
several addons frequently do something foolhearty like doing a timer.Create and losing track of the things they were meant to apply or being interrupted by a round lifecycle event like a round ending -- or more likely not being interrupted when they should be.
some examples:
Describe the solution you'd like
the fundamental problem has two main components:
Thus the solution should be shaped like:
and behind the scenes we:
I didn't include all the timer arguments here for brevity but the idea is apparent: create a superset of that API more tightly coupled to the lifecycle of entities via extending the EntityMeta or whatever. Special handling may be warranted by making the implementation for PlayerMeta different.
Describe alternatives you've considered
there is no way to stop people from making chatgpt-tier addons
The text was updated successfully, but these errors were encountered: