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

How about a custom register name? #281

Open
Ecdcaeb opened this issue Mar 16, 2024 · 2 comments
Open

How about a custom register name? #281

Ecdcaeb opened this issue Mar 16, 2024 · 2 comments

Comments

@Ecdcaeb
Copy link

Ecdcaeb commented Mar 16, 2024

Usually, what we register using cot, used the register name whose domain is contenttweaker.
How about a custom register name, which enable modder put a ResourceLocation instead of a String to expand the domains of register names.

@kindlich
Copy link
Collaborator

We deliberately made it so that all blocks are registered under the contenttweaker namespace.

Reason for that is so that nobody registers items under another mods' namespace.
This is so that nobody raises an issue at another mod for items that were added via ContentTweaker.

Can you give a bit more context of why the modid is important in your usecase?

@Ecdcaeb
Copy link
Author

Ecdcaeb commented May 19, 2024

Under normal circumstances, it is enough to use contenttweaker, but sometimes we may want some personalized content or traceability, especially Custom load source or In Pack script, although CrT did not implement these two in 1.12.2.

I made a Mod to implement these two parts, and customized domain is also a normal requirement. Oh, is just a hope. If this is not considered Cot's responsibility or plan. You could close it.

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

2 participants