Closed deltaconnected closed 5 years ago
Today's build can generate "new" logs if you add in a new_cbtevent=1
key under [main]
in the ini. I didn't actually test it (but given nothing broke I assume it works)
Thanks! Do you have a plan on when you're going permanently switch over?
Nope. Still plenty time before we hit the skillid ceiling, so I've no problem waiting til everyone's got their code in place. The only thing I can't do with the old struct is cast my way to storing 6 floats for effect info but that was rip anyway for now - position logging was also denied originally
Version 2.2.6 released on 2018-10-05 10:41:35
The last 3 episodes have bumped skill ID's from 40,000 (expansion) to 52,500 (this LS episode) so I've got probably half a year before the cbtevent struct blows up (skillid > u16 max). There's plenty that could be nice-ified in evtc but until there's some hard limit I'm leaning towards keeping what works.
What it is now:
What it will likely be:
Notably skillid us up to u32, overstack_value is up to u32, a matching dst_master_instid was added, and my internal sorting/tracking bytes were removed. In theory it should be as easy as using the "new" struct and writing a cbtevent.=cbtevent1. operator or function to assign everything if old revision.
It's not set in stone yet but will probably be how it ends up, I'll b watching this for comments and suggestions