Azanor / thaumcraft-suggestions

This area is specifically to post any suggestions or balance issues. The main area should be kept for bug reports only.
31 stars 12 forks source link

Please add aspect specific metadata to flux in chunks, and an api to access it. #358

Open mopsyd opened 6 years ago

mopsyd commented 6 years ago

So I'm not going to ask you to create a ton of aspect specific flux effects, because that would be over the top. However, tracking the specific aspects that created flux, and providing an api to hook into would allow addons and other mods to do so (eg slow plant growth for herba, accelerated durability reduction for metallum, etc).

I think creating a ton of case-specific features such as this in the core thaumcraft mod would be a bit bloated and a huge time sink, but it's an interesting concept to hook into.

Thunder-Nova commented 6 years ago

This might not be much of a bad idea, but from what I can imagine it will change a lot in some mechanics.

But I imagine a flux dimension using that idea. Gear to survive that dimension (especially if inside mortis flux biome). And some rewarding loots.

mopsyd commented 6 years ago

I had not really envisioned any direct changes to gameplay, although I'm sure it would change a bit about the class structure under the hood. I think it could be implemented in a way that is not disruptive to the current Thaumcraft play mechanics, but provides for a pretty versatile set of options for extension. I think it would encourage a lot of supporting addon mods, but should probably not alter the expected thaumcraft gameplay without addons if possible. It would probably be best to provide both the raw "total" flux level without aspects, as well as an optional more granular aspect-specific set under a separate request, which would allow logic to work with either the existing mechanics or the aspect specific ones as use-case warrants. I think it would remain the most backwards-compatible to offer both, with the existing api presiding as the default.

Perhaps there is something in the ore dictionary codebase that might make this easier, or at least provide a basis for creating the api for it.