SteamWar/ProtocolLib
Archiviert
13
0
Fork 0
Code Issues Pull-Requests Releases Wiki Aktivität

Clarify the compatibility section

Quellcode durchsuchen
Dieser Commit ist enthalten in:
Dan Mulloy 2014-12-02 16:20:03 -05:00
Ursprung 5b9acb72fb
Commit dabbe3fca9
1 geänderte Dateien mit 4 neuen und 5 gelöschten Zeilen
Statistiken anzeigen Patch-Datei herunterladen Vergleichs-Datei herunterladen Alle Dateien ausklappen Alle Dateien einklappen

9
Readme.md
Datei anzeigen

@ -133,19 +133,18 @@ try {
} }
```` ````
Compatiblity Compatibility
------------ ------------
One of the main goals of this project was to achieve maximum compatibility with CraftBukkit. And the end One of the main goals of this project was to achieve maximum compatibility with CraftBukkit. And the end
result is quite flexible - in tests I successfully ran an unmodified ProtocolLib on CraftBukkit 1.8.0, and result is quite flexible. Aside from netty package changes, it should be resilient against future changes.
it should be resiliant against future changes. It's likely that I won't have to update ProtocolLib for It's likely that I won't have to update ProtocolLib for anything but bug fixes and new features.
anything but bug and performance fixes.
How is this possible? It all comes down to reflection in the end. Essentially, no name is hard coded - How is this possible? It all comes down to reflection in the end. Essentially, no name is hard coded -
every field, method and class is deduced by looking at field types, package names or parameter every field, method and class is deduced by looking at field types, package names or parameter
types. It's remarkably consistent across different versions. types. It's remarkably consistent across different versions.
### Incompatiblity ### Incompatibility
The following plugins (to be expanded) are not compatible with ProtocolLib: The following plugins (to be expanded) are not compatible with ProtocolLib: