Why would you change the structure? All you've done so far is change "RTB" to "oRBs" if that addon's correct, just maintain compatibility throughout the life of the project so it doesn't aggravate any future users.
The simple fact that my server infrastructure is different than RTB has made the mod manager not functional with the original RTB.
My hopes are to evolve on this project, and by choice I do not wish to support RTB prefs it might not change as it might.
You may use the great add-on that _Crispy made, run the converter or not use oRBs at all.
The choice is yours :) this is a free world. You are looking for problems where there are none.
If any add-on devs use RTB prefs in their current, still maintained addons, all the converter will do is put hassles on the end-user.
Devs have the ability to post their add-ons to oRBs and will soon have the ability to maintain their downloads, so no hassle for users.
Also add-ons can, if they are maintained, easily support both oRBs or RTB as shown in this example from Kyuande's
Server AFK Emote:
if(!$Server::AFK::CheckVals)
{
if(isFunction(ORBS_registerPref))
ORBS_registerPref("Check (seconds)", "AFK Mode", "$Server::AFK::Check", "int 1 1800", "Server_EmoteAFK", 60, 0, 0);
else if(isFunction(RTB_registerPref))
RTB_registerPref("Check (seconds)", "AFK Mode", "$Server::AFK::Check", "int 1 1800", "Server_EmoteAFK", 60, 0, 0);
else
$Server::AFK::Check = 10;
$Server::AFK::CheckVals = 1;
}
What if there's an update? They'd have to run it through a converter/function renamer (at this point?) every time. I would just head back to RTB in that case just so prefs work.
Updates are managed automatically through the mod manager. I guess that escaped you in the last post for you.
If ever things were to change, add-ons in the oRBs database would be updated accordingly eliminating the "hassle" to users.
This has been made for users, and hopefully will give all of you something like the great add-on we used to love.
Any existing add-ons using the rtb prefs API should continue working without the end user doing anything. Why would you make it more complicated?
And they can, I am simply not keeping any function in reference to RTB. Things will work as it was for users. if anything once the add-on database is loaded it will remain as easy as it was. The RTB to oRBs converter allows to prep add-ons so that the ID's will match on the oRBs database and if an update is posted it will be able to auto-update for users.
If you are not willing to use oRBs because you find it too complex to replace an add-on then you can stick with the old RTB.
Thank you for your comments.
