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

[Suggestion] Allow configuration of the mod through data pack tags #688

Open
Not-February opened this issue Jul 6, 2024 · 0 comments
Open

Comments

@Not-February
Copy link

Not-February commented Jul 6, 2024

I've enjoyed this mod for a very, very long time - but I think it is perhaps at last time to admit that the config system it currently uses has become archaic by modern modded MC standards.

I think it would be a lot easier for end users/pack developers to manage Reliquary in a larger modded ecosystem with datapacks than it is to use the current default configs.

Plus, with conditional data files, other mods could potentially add their own optional built-in support for Reliquary much more easily. This ranges from QOL to avoiding actual game-crashing problems like #684 brings up.

I don't know how hard it would be to convert everything over to this kind of system, but it would be nice! I'm not against the config option sticking around for those who prefer it.

Things currently in the config that would be easier to configure with item/entity/block tags:

  • Mob Charm entity blacklist
  • Interdiction Torch entity/projectile blacklists
  • Seeker shot entity blacklist
  • Rod of Lyssa entity blacklist
  • Rending Gale pushable entity/projectile blacklists
  • Valid torches for the Lantern of Paranoia/Sojourner Staff
  • Touchstone of Midas golden items
  • Destruction Catalyst mundane blocks
  • Apothecary Cauldron heat sources
@Not-February Not-February changed the title [Suggestion] Allow configuration of the mod through data pack item/entity tags [Suggestion] Allow configuration of the mod through data pack tags Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant