-
Notifications
You must be signed in to change notification settings - Fork 47
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
Added spherecustom.ini definition #1310
base: dev
Are you sure you want to change the base?
Conversation
That mean if value are at 2 places server will priorize spherecustom.ini? |
Yes, if you put any data in spherecustom.ini, will override the value in sphere.ini, for example if you put ServName to MyCuteServer like in example, even it's MyShard in sphere.ini, <SERV.NAME> will return as MyCuteServer |
…ms without a set price to return as -2,147,483,648. (Issue: Sphereserver#1233)
…e restriction of being TILEDATA value is removed. (Issue: Sphereserver#1301)
Actually i don't really get the usefulness of this proposed feature (spherecustom.ini), because sphere already has hardcoded defaults for every ini setting. It reads the ini file and overwrites the defaults with the values it finds in that ini, otherwise it uses the defaults it already has. It's already done in that way, as far as i can see. |
I added that because I thought same but while I was testing Sphere crashes automatically without giving an error on launch when you just put
values inside. |
Okay anyway I noticed the issue is because of one/couple of these definations;
Edit: seems like if you don't define map0 in sphere.ini it loops infinitely and crashes sphere on launch. |
This allows you to override Sphere settings without touching the Sphere.ini file.
For example, when you want to switch from an older Sphere version to 56x or when you haven't updated for a long time, instead of checking all the new data added to Sphere.ini one by one, you can simply use your old sphere.ini as spherecustom.ini. This way, newly added data will take the default settings from Sphere.ini, while your previous custom settings will override the defaults without requiring any further adjustments.
On the other hand, it helps you maintain a clean Sphere.ini. Instead of directly changing the Sphere.ini settings, you can create a spherecustom.ini file and add only the settings you want to change there, allowing you to easily track the changes without modifying Sphere.ini.
Here's an example of a spherecustom.ini:
Fixed: The mismatched default value check was causing the price of items without a set price to return as -2,147,483,648. (Issue: #1233)
Changed: Now CHARDEFs can read custom Item Resources as an ICON, the restriction of being TILEDATA value is removed. (Issue: #1301)