1.5.2 - Making changes to singleplayer & server + versioning

[jacobferrante]

If I was to make a change in the minecraft/src, say like editing the BiomeBaseGen
minecraft/src/net/minecraft/src/BiomeGenBase.java

Would I have to make the same changes in the server side?

minecraft_server/src/net/minecraft/src/BiomeGenBase.java

This is of course if I wanted to a run a server with this modded version.

Also how are people handling versioning in a legal way? and how are you setting up your directories? Do you track just the minecraft/src/ directories or do you start at the root directory containing all the sub directories? (build, conf, jars, libraries minecraft, minecraft_server )

[PhoenixVX]

Versions after release 1.3 use the same obfuscation mapping for both the client & server. The easiest way is to decompile the client/server with the "Merged" side for versions after release 1.3 (and a few select Alpha versions which have mergeable mappings).

Otherwise, you do have to commit edits to both sides to be fully functional and avoid desyncs/crashes. In general, it is not recommended to track the source folders in Git as that can be considered as redistributing Minecraft's source code which is against the EULA. If you must share your code, I recommend using the "Create patch" task which generates a file which contains only the differences/changes you have made and can be applied using the "Apply patch" task.

If you are hosting a private Git repository, it is "acceptable" to host the src folder but the other folders would not be very useful as they are dependent on JVM version being consistent to apply correct patches for reobfuscation which is usually not consistent.