Closed mgejay closed 7 years ago
This seems to be okay, there is no nick blacklist however.
The blacklist should be stored as part of the settings table in mySQL
@Wild1145 That would create more data for no reason. The blacklist doesn't disappear on a reload or restart like HashMaps and ArrayLists, this is always there and works just fine, no need to create more work and fix something if it isn't broken.
@Adaptified It does however need to be centrally stored and able to be updated in real time as we need.
@Wild1145 You're developers, it's not hard to edit the code. That's why github is here, people suggest something and then it happens. Not everything needs to be SQL.
@Adaptified The entire point of this project is that it is fully SQL based, no configigs and everything is global. I and @CameronRedmore may be Java developers, but @TheCJGCJG is not, neither is Varuct, so if they want to make a change, they have to wait for me or Camzie to be free, make the change, test the change and then push and compile. We then have to take the network offline to update it. Or we just follow the project goals to SQL everything and make one minor change to a table and boom, done.
@Wild1145 Done.
The blacklist this takes is simply a comma delimited list in the format: "Admin, Mod, Super, Senior, Telnet, Developer, Manager, Executive, &k, &o, &n, &m, &1, &0" for example. If this string is entered as the value for a new row in the 'settings' table which is named 'blacklist' all of those terms would be blacklisted.
Holy formatting issues. I am guessing you want the bracket under the statement.
@Adaptified It should be in allman style. Just like TFM.
@Wild1145 All done.
Solves #177