search

Rickedb / OpenProtocolInterpreter

Converts the ugly ASCII package that came from Open Protocol to an object
MIT License
144 stars 72 forks source link

Questions on Protocol and Specification Versioning #106

Closed dekenless closed 8 months ago

dekenless commented 8 months ago

Below is the description from the OP documentation no how they do version, release & revision specification -- when using the OpenProtocolInterpreter it appears that one only really needs to be concerned with the revision when dealing with specific MIDs (i.e. the version and release are more or less irrelevant). Is that correct?

I regards to OP 2, that largely seems to be additional MIDs and dealing with variable message data size--is OP 2 supported?

image
Rickedb commented 8 months ago

Hi @dekenless, you're right, the OpenProtocolInterpreter version has no relation with OP versioning. Since we might face bugs that has no relation with the protocol itself (an internal bug for example), it would be difficult to keep versions equal and would cause more confusion. (If you have a suggestion on how to handle this, I would appreciate it)

As far as I know, most of MIDs are compatible with previous versions and the lib is not handling these compatibility issues yet.

The reference of OP version for the latest release of OpenProtocolInterpreter is 2.14.0 (see docs here). If there is another version published, I would ask you to provide the docs, so I can develop the new modifications or new MIDs at the library. Optionally, you can do it by yourself and make a PR too.

Check unavailable mids section for further information on which are not implemented (most of them due to lack of example for testing).

dekenless commented 8 months ago

Thanks for the reply.

Attached is the latest version that I know of, 2.17 I believe. OpenProtocol_Specification_R_2.17.0.pdf