PGM
PGM copied to clipboard
PGMDev
Sync map protos with plugin versions
With the release of 1.8 PGM, some modules have been added and others have been scrapped. The old proto versioning is obsolete and we need a new way to specify what PGM version an XML file was created for.
You would still need to support protos for older XML, why not just jump to 5.0?
I support this in principle. I think the best solution is to figure out a new keyword to replace "proto". Maps can use that keyword to define which OS PGM version they're using. Otherwise maps using legacy proto's will still work.
IMO proto should be kept. Proto itself just needs to change for breaking changes, that means, if behaviour would change on an already made map without changes to it's xml, it should be a proto bump, that means new maps will work that way but older ones will keep working with the older behaviour.
Adding a new module doesn't mean bumping the proto, as long as any older map is not affected by it unless it's used.
OS PGM should just implement/backport up to proto 1.4.2 and continue from there if any breaking changes are added
We'll need to support both, so I think we can do this:
proto is the old system.
version is the new system, starting with 1.0
To me, version seems to imply that one map made for one version would only work with one pgm version
My bigger issue with version is that it conflicts with the version tag already present in the XML files which refers to the version of the map itself.
Surely we would want to keep everything in sync. Implementing 1.4.2 features should be the goal, maps are backwards compatible, and proto changes only happen for breaking things.
I don't think we should be encouraging spoons or future updates that brake legacy maps because they want to mess around with protocol versions.
Maybe I'm misunderstanding what issue is about. It should be assumed servers are running the latest plugin version and all new versions support previously valid maps.
