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

Preferences touch-up... again... #12

Merged
merged 10 commits into from
Oct 14, 2016
Merged

Preferences touch-up... again... #12

merged 10 commits into from
Oct 14, 2016

Conversation

ShockFromBL
Copy link
Contributor

See commits' desc's for further information.

- checks server.cs file CRC to see if it's a dummy one that
Support_Preferences has placed.
- changed default allowed rank to superadmins.
- preferences which weren't conforming to the "$Pref::Server::"
standard, and preferences which required a restart altogether now save
and load properly.
- prefs now clean themselves up properly, so you won't see preferences
for disabled add-ons showing up in something such as Glass Server
Settings.
- made the echo's colored/neater.
- added version echo.
- changed some variables which weren't conforming to the standard set by
badspot in patch notes e.g: .name instead of .getPlayerName()
- messageall preference changes now displays all preferences categories
changed.
- fixed some functions not using BLP_isAllowedUse() which could cause
potential issues with preferences not being use-able.
- added prefs backup just in-case...
- set version number to 1.2.0
- number of addons which had preferences and are now echo'd to console.
- forgot to change function syntax for general server preferences (added
a %filename parameter for pruning).
- fixed a minor visual issue in chat when updating preferences of the
same category twice in a row.
@ShockFromBL ShockFromBL reopened this Sep 25, 2016
- self explanatory.
...
- fixed typo(s) in pruning functionality preventing its operation.
- removed potential console errors arising from prefs never registered
before.
- forgot to pull first before adding changes.
- let's try this again.
...
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

Successfully merging this pull request may close these issues.

None yet

2 participants