



Joe90
Very odd. I will try and get to the bottom of it ASAP.
Try this:
lang.RegisterMessages(en, this);Instead of:
lang.RegisterMessages(en, Instance, "en");Note: You can leave the "en" if you want, it's the assumed default though.
I've tried to implement that. I've also added some logging so you should see a message in the server console that reads "Registered language for 'en'" when LoadDefaultMessages is run.Wulf
Try this:
lang.RegisterMessages(en, this);Instead of:
lang.RegisterMessages(en, Instance, "en");Note: You can leave the "en" if you want, it's the assumed default though.
Wulf
Try this:
lang.RegisterMessages(en, this);Instead of:
lang.RegisterMessages(en, Instance, "en");Note: You can leave the "en" if you want, it's the assumed default though.
There are few problems with language system after last updates. Its adding new values in language file, but it doesnt seems to detect them in oxide core
Orange
There are few problems with language system after last updates. Its adding new values in language file, but it doesnt seems to detect them in oxide core
It wouldn't magically have issues when there have been no changes... Not aware of any either, and this issue does not appear to be "new", just a null Instance.
Joe90
I've tried to implement that. I've also added some logging so you should see a message in the server console that reads "Registered language for 'en'" when LoadDefaultMessages is run.
The reason for my example is that your Instance isn't set before that method is called I believe, so it would be null and your messages wouldn't be registered to your plugin.
Wulf
The reason for my example is that your Instance isn't set before that method is called I believe, so it would be null and your messages wouldn't be registered to your plugin.
Ah missed that Instance was still in there (and misread what you wrote :S ), meant to swap that out when I moved it. Will correct it and re-release it.
Thanks Wulf