Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design the process of making custom texture packs (and skins too?) to be easy and modular. #16

Closed
Hunternif opened this issue Nov 11, 2014 · 4 comments
Assignees
Labels
type: enhancement This is a clear improvement to the mod type: mod interaction An issue in conjunction with another mod

Comments

@Hunternif
Copy link
Member

No description provided.

@Hunternif Hunternif added the type: enhancement This is a clear improvement to the mod label Nov 11, 2014
@Hunternif Hunternif self-assigned this Nov 11, 2014
@Hunternif
Copy link
Member Author

Tiles use texture sets exclusively, abolishing individual textures.

@Hunternif Hunternif added the type: mod interaction An issue in conjunction with another mod label Feb 13, 2015
@Hunternif Hunternif removed their assignment Dec 17, 2015
@Hunternif
Copy link
Member Author

Hunternif commented Jan 3, 2017

DRAFT SOLUTION, WIP

It would be nice to use String names instead of int IDs to identify Biomes, but inside Atlas a biome must be represented as a number internally, and there's no need to break backward compatibility of the configs.
TODO find a way to use String names in configs.

The following is a chain of biome texture configs order by increasing precedence:

  1. The mod has its default texture config with 1) definitions of texture sets and 2) biomes assigned to texture sets. These files will be saved externally in json format as reference for modders, and also to let the player modify this config it manually. Deleting the files will cause them to be regenerated with default values.

  2. Any world (SP or MP) may have its own set of the same configs, which will override defaults. Any calls to the API from other mods will only modify this config, and therefore must be called every time a new world is created. One use case for this may be if a texture may change depending on some condition that can change online. TODO other mods shouldn't make redundant calls to the API. Will the need ever arise for modifying biome configs from their defaults at runtime?

  3. Any other mod or resource pack may have its own configs of this kind, which will override the default configs and world configs. A resource pack may override existing textures?
    TODO a resource pack may be plugged IN and OUT of any world.

An identical chain should apply to marker configs.
Make sure config files are never physically overwritten, see #36.

@Faedelity
Copy link

I am very happy to see this is in process. I am quite willing to help test if that is useful. I am running primarily Minecraft 1.7.10, but I can make a profile for any version easily for testing purposes.

@tyra314
Copy link
Member

tyra314 commented Apr 12, 2021

This was superseded by the new resource pack based configuration: https://github.com/AntiqueAtlasTeam/AntiqueAtlas/wiki/Resource-pack-based-Texture-Config

@tyra314 tyra314 closed this as completed Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement This is a clear improvement to the mod type: mod interaction An issue in conjunction with another mod
Projects
None yet
Development

No branches or pull requests

3 participants