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
This extra entity system is very wasteful and we can actually (re)use a lot of fields within the entitystate and playerstate if needed, as ET has a ton of extra free unused fields on player types and in general in ETF they are not used at all.
Hello, please excuse me if I'm totally wrong, but wouldn't be UEIDs perfect for fixing this?
Tremulous uses UEIDs.
I assume it would be hard to completely rewrite ETF's entity system to match the Tremulous style of how to deal with entities. Anyways, would it be worth at all?
I have to admit I don't have the skills, to make that happen. It just crossed my mind and I followed Tremulous for a while and saw that they really spent a lot of time to improve the entity system and memory managemant.
I have not currently pushed the changes yet, but I have already fixed the corpse task and the gas hallucination task. Haven't pushed because not yet confident I have done it right without more clients available to testing.
This extra entity system is very wasteful and we can actually (re)use a lot of fields within the entitystate and playerstate if needed, as ET has a ton of extra free unused fields on player types and in general in ETF they are not used at all.
The text was updated successfully, but these errors were encountered: