Change texture definitions for Java Blueprints

A new update is now available, introducing a lot of new content!
Latest hotfix: 0.7.5.2 (2024-09-10)
  • The new Version is capable of loading Java blueprints - but it doesn't use the same textures as the Java version, so the final building may look different in the new version.


    If you think some replacement textures aren't suitable, you could set up a text file called "JavaTextures.txt" in the game directory, where you could define your own texture definitions. Set up one texture per line, containing the old Java ID and the new texture ID it should be replaced with, e.g. 32 = 300 to replace Java ID 32 with ID 300 in the new version. Optionally you can also provide a hex color code (either 0xRRGGBB for the full color, or additionally provide the intensity like 0xRRGGBBAA), e.g. 32 = 300, 0xFF0000 for a red colored block, or 32 = 300, 0xFF000080 for half red color. In addition to this, you can also provide a texture scale, e.g. 32 = 300, 0xFF0000, 2.0 for a red colored block with a texture scale of 2.


    If you put a # at the beginning of a line, you can add comments (i.e. this line will be ignored by the game). Example:

    Code
    # Wood textures
    64 = 101
    67 = 120, 0xFF0000
    84 = 139, 0.5
    # Metal textures
    175 = 702
    178 = 740, 0xFFFFFFAA, 0.25


    You can either replace all textures, or just individual textures (e.g. if you just add a single texture to the JavaTextures.txt file, the game will only use it for this particular texture and fall back to the default definitions for all other textures).


    Here you find the current default setting for all textures: JavaTextures.txt



    :!: IMPORTANT: Changing the textures only works for newly added Java blueprints. If you load a Java blueprint in the new version, it gets converted to the new format automatically, so changing the texture definitions won't have an effect on this blueprint anymore :!:


    You can disable this behaviour by setting Game_BlueprintsConvertJavaBlueprints to False in the config.properties file - but this may increase loading times if you have lots of Java blueprints.



    The default definitions may not be perfect, so if you have any suggestions for particular textures (e.g. if there may be an existing ID or color that could be more appropriate), please let us know so we can change the default definitions accordingly :)

Participate now!

Don’t have an account yet? Create a new account now and be part of our community!