[trevius]

I am not really sure what the plan is for this client. I don't really think we have enough active devs interested in maintaining a client that keeps up with Live patching. Though, with some recent scripts I made, updating opcodes is a bit easier. That may make it possible to keep up with Live with minimal work as long as it is kept up with for each patch so we don't get too far behind. The further behind we get, the harder it is to catch up, as many packet structures have changed and it takes a while to account for them all and fix them.

One thing I want to mention is that I named the patch files "VoA", which is the same naming convention as our previous clients. The difference is that this client could change at any time due to its source. So, one issue that would need to be dealt with if we tried to keep up with Live is how to handle the patch files in our source. We could have the names change to reflect the date of the eqgame.exe build date, or we could just put that date in the patch file as a comment and name them something like "VoA1", "VoA2" and so on. It isn't the naming that concerns me too much though, it is the number of potential patch files we would eventually have. It is already enough of a pain to update 4 patch files for every new opcode that gets added. I don't even want to think about having to do 20 of them after just 1 year of "chasing Live"! Maybe some sort of sub-patch system could be created that would allow for minor changes within the same expansion of patches. I think we would need some kinda change like that or maybe only support new opcode additions for the current patch as well as the UF and older clients and skip any Live patches in between.

I am just hoping that Steam gets a new complete client for EQ again at some point. If they do, then the work on this VoA client might be able to get the Steam version running in minimal time. That is my main reason for working on this client right now.