Getting ready for 2.0 & Quality of Life changes
This commit is contained in:
parent
b0f364399b
commit
d94d1d8956
10
README.md
10
README.md
|
@ -8,6 +8,16 @@ When working with blocks, the convention is such:
|
|||
1. The BlockEntity will impliment the INode/IAcceptorNode/IProviderNode interfaces.
|
||||
2. The Placed block will ask the blocks around it to become a provider and or an acceptor, not the other way around.
|
||||
|
||||
(These conventions assume a server-side approach to your mod's pipes implementation)
|
||||
|
||||
### Note from the author
|
||||
I won't try to update the requirements for the API too much, so it should keep consistant across MC versions. However, when a common requirement is determined, I will update the API. This can be determined by the major version of the mod.
|
||||
|
||||
API updates/upgrades will only happen on Minecraft version increases (i.e. 1.16 -> 1.17, but not 1.16.4 -> 1.16.5) so all versions of the mod will work with other mods for the same MC version.
|
||||
|
||||
First few changes may come quickly as the API stabilizes, but by version 3 or 4 I think there will be a lasting API.
|
||||
|
||||
Release Candadites or Beta versions may or may not reflect the release API.
|
||||
|
||||
## License
|
||||
This mod is available under the MIT licence.
|
||||
|
|
Binary file not shown.
After Width: | Height: | Size: 15 KiB |
|
@ -1,7 +1,7 @@
|
|||
{
|
||||
"schemaVersion": 1,
|
||||
"id": "transit-api",
|
||||
"version": "1.0.0",
|
||||
"version": "2.0.0",
|
||||
|
||||
"name": "Transit API",
|
||||
"description": "Move things about!",
|
||||
|
@ -15,7 +15,7 @@
|
|||
},
|
||||
|
||||
"license": "MIT",
|
||||
"icon": "assets/transit-api/icon.png",
|
||||
"icon": "assets/transit-api/transit.png",
|
||||
|
||||
"environment": "*",
|
||||
"entrypoints": {
|
||||
|
|
Loading…
Reference in New Issue