4.1 KiB
Updating instructions for the project
Update translation files
Translation files are located in src/main/resources/assets/viafabricplus/lang/
. To update them, you need to do the following:
- Copy the
en_us.json
file and rename it to the language code of the language you want to update (e.g.de_de.json
for German) - Translate all values in the file to the language you want to update
- Do not change the keys of the values, only the values themselves
- Do not change the formatting of the file (e.g. the spaces between the keys and values or the order of the keys)
- Try to be consistent with Minecraft language files.
- Take a look at UN's guidelines for Gender-inclusive language: https://www.un.org/en/gender-inclusive-language/guidelines.shtml
- Create a pull request and wait for it to be reviewed and merged.
- You're done, congrats!
Add a new feature or fix a bug
- Create a new branch for your feature/bugfix (e.g.
feature/fix-xyz
orfix/fix-xyz
) - Implement your feature/bugfix and make sure it works correctly
- Clean your code and make sure it is readable and understandable (e.g. use proper variable names)
- Use the Google java code style (https://google.github.io/styleguide/javaguide.html) and format your code accordingly
- If you're changing API, make sure to update the documentation in the
docs
folder, add javadocs to your code and don't break backwards compatibility if not necessary - Increment the version number in
gradle.properties
by at least a patch version (e.g. 1.0.0 -> 1.0.1) - Create a pull request and wait for it to be reviewed and merged.
- You're done, congrats!
Update to a new Minecraft version
-
Update all upstream versions in
gradle.properties
. The main versions you need to update are:minecraft_version
yarn_mappings
loader_version
fabric_api_version
viaversion_version
viabackwards_version
mod_menu_version
-
Update the
NATIVE_VERSION
field in the ProtocolHack class to the new version -
Check all mixins in the injection package if they still apply correctly, here is a list of some critical ones:
MixinClientPlayerEntity#removeBl8Boolean
MixinClientWorld#tickEntity
andMixinClientWorld#tickPassenger
MixinPlayer#getBlockBreakingSpeed
-
Decompile the game source code with the tool of your choice.
-
Check all data dumps and diffs in the fixes/data package and update them if necessary, here is a list of some critical ones:
ResourcePackHeaderDiff
(add the new version at the top of the list)ItemRegistryDiff
(add all new items/blocks added in the new version)
-
Diff the game code with the code of the previous version (e.g. using git) and implement all changes that could be relevant for ViaFabricPlus, those are:
- General logic changes (e.g.
if (a && b)
->if (b || a)
) - Changes to the movement code (e.g.
player.yaw
->player.headYaw
) - Networking changes (e.g. sending a new packet / changing the packet structure)
- Changes to visuals (e.g. animation changes)
- Note: ViaVersion already implements most gameplay related changes for us, but you should always check for edge-cases. Since ViaVersion is primarily a server side plugin, it does not take care of client-side related / deeper changes.
=> If you are unsure if a change is relevant, ask in the ViaVersion discord, in general you should only implement changes which could be detected by a server side anti cheat.
- General logic changes (e.g.
-
Check the ViaVersion/upstream protocol implementation for issues and report them if necessary or if these issues can't be fixed, without tons of work, implement a workaround in ViaFabricPlus.
-
Run the game and check all GUIs and other visuals for issues.
-
Clean your code and make sure it is readable and understandable, clientside fixes are sorted by their protocol versions, having newer fixes at the top of the file.
-
Increment the version number in
gradle.properties
by at least a minor version (e.g. 1.0.0 -> 1.1.0) -
Create a pull request and wait for it to be reviewed and merged.
-
You're done, congrats!