|
I'll preface this by saying I've no interest in post-3XX file formats
What's the general consensus on breaking compatibility with 317 formats and just rolling our own? Given that it seems most client/server pairs nowadays are incompatible with one another, why not just stop trying to replicate the proprietary formats used by Jagex circa. #317, and just fork the client to agree on a standard, extensible format?
Same could apply to 4XX and 5XX. We'd just agree on a format which encapsulates all of the information we need for all versions, and use the same data regardless of client version.
We could then just write a set of tools which work with this 'unified' set of formats, and be done with (poorly) reverse engineering and emulating formats forever.
Thoughts? Am I completely off base? I've been out of the 'scene' for years, is there some obvious restriction to this I'm missing?
Tom
Nice idea, would contribute
I've been thinking about this for a LONG time actually lol. Good thing someone has finally proposed the idea.
Whats wrong with the original 317 formats, they're compact, fast, and are already supported by all 317 clients out there without (or with few) any additional modifications. Why change that which already works perfectly fine?
Sounds like a good idea to work off of
For almost all of my previous client related projects, I've always adopted the same approach of simply just getting rid of any Jagex formats which stand in my way, and then just replacing it with an alternative.
There really is no reason to religiously stick to the original formats (especially if they start to become a hindrance), and I think it would be nice to try and push the community towards new unified sets of formats.
this would only work if there is a set of tools and basic client (MITB 317 Deob), that uses this new format and everyone must see that it goes far beyond what the 317 client can do.
Issue is for me is that I update very often to a more later client to keep up with current rs3 updates, such as client big fixes and such, so this wouldn't be the best idea for me, however for people who are sticking with a single version, for example 317 then it would be better as they will more likely never update to a later protocol version. The issue is with this concept is, someone who does not use your format, then the tools are useless, so it may be better to put the time of making a new format into actually figuring out the official format.
yeah i would much prefer tools to import and export to readable file formats, such that you can edit them in a nice tool or readable file, then pack them back to the cache in the format the client expects
could modularise it for each revision too (having an encoder and decoder for each revision)
« Previous Thread | Next Thread » |
Thread Information |
Users Browsing this ThreadThere are currently 1 users browsing this thread. (0 members and 1 guests) |