Howdy, Stranger!
Categories
- 4.8K All Categories
- 4.3K Life in Lusternia
- 465 Announce Posts
- 75 Event Posts
- 1.7K Common Grounds
- 589 Q&A
- 83 Combat Overhaul
- 1.5K World Library
- 86 Combat Logs
- 870 Event Scrolls
- 403 Mechanic's Corner
- 329 Ideas
- 314 Last Chance Trading Post
- 478 Life Outside of Lusternia
- 9 Forum News
- 275 The Real World
- 94 Meet and Greet
- 37 The Funnies
- 63 Mafia Hideout
Standalone NameDB
Falaeron
Jolteon
NOTE: THIS PACKAGE CAN BE CONSIDERED TO BE IN BETA. IT IS VERY POSSIBLE THAT IT WILL BREAK SOME THINGS FOR YOU. YOU HAVE BEEN WARNED.
So you have likely heard by now that server-side curing will be a thing soon(tm) and around that time Shuyin will no longer be updating mmf. It is unlikely that anyone else will pick up the bulk of the development of the system. While curing is why most people install mmf, there are a few other very handy packages such as the NameDB that many of us use regularly. However, the NameDB that comes with mmf is very much dependent on also having mmf installed so will not be able to use it without also keeping some of the core functionality of mmf. As such, I set out to adapt the package to work on its own. I imagine many of you are also wondering what you can do to keep using the ndb after mmf is no longer updated, so I decided to share it with everyone.
Please note that I primarily wrote this for myself and while I did ask around to see what things people used, I did strip out most of the things that I didn't ever see a need for. It also no longer uses honours at all to get any information and relies entirely on the Lusternia api. If you ever used the stuff like the notes then I'm afraid you'll be out of luck here. The primary function is really just to keep track of what org people belong to and highlight accordingly.
The list of api functions I ported over are: isglom, ismag, iscelest, ishalli, isgaudi, isseren, exists/isperson, getname, isenemy*, isorgenemy*, getnamebytitle, findname, findnames, getpluralorg, getcolor*, getcolorp*
*I changed how isenemy, isorgenemy, getcolor and getcolorp worked a bit to make more sense for myself. They still work for the scripts I put them into so hopefully they work for you too.
Download:
https://www.dropbox.com/s/2xb1kyvc1u7d1pj/NameDB.zip?dl=1
Installation instructions:
1a. If you are using mmf: go through the triggers, aliases and scripts and disable/delete the NameDB folders. This step is very important and you will need to do this every time you update mmf.
1b. If you are not using mmf: ensure your profile has gmcp turned on.
2. Restart the profile.
3. Install the package through the package manager.
4. Restart the profile again.
The alias ndbc is more or less what mmconfig politics used to do.
To-do:
-Fix bugs that are certain to exist
-Do stuff with guilds. Maybe show them in CWHO.
-Other things that I wanted to do but forgot about at this time
Credits:
-Vadi for the original ndb which I stole a lot of the stuff from.
-All the contributors who have helped upkeep mmf in general.
So you have likely heard by now that server-side curing will be a thing soon(tm) and around that time Shuyin will no longer be updating mmf. It is unlikely that anyone else will pick up the bulk of the development of the system. While curing is why most people install mmf, there are a few other very handy packages such as the NameDB that many of us use regularly. However, the NameDB that comes with mmf is very much dependent on also having mmf installed so will not be able to use it without also keeping some of the core functionality of mmf. As such, I set out to adapt the package to work on its own. I imagine many of you are also wondering what you can do to keep using the ndb after mmf is no longer updated, so I decided to share it with everyone.
Please note that I primarily wrote this for myself and while I did ask around to see what things people used, I did strip out most of the things that I didn't ever see a need for. It also no longer uses honours at all to get any information and relies entirely on the Lusternia api. If you ever used the stuff like the notes then I'm afraid you'll be out of luck here. The primary function is really just to keep track of what org people belong to and highlight accordingly.
The list of api functions I ported over are: isglom, ismag, iscelest, ishalli, isgaudi, isseren, exists/isperson, getname, isenemy*, isorgenemy*, getnamebytitle, findname, findnames, getpluralorg, getcolor*, getcolorp*
*I changed how isenemy, isorgenemy, getcolor and getcolorp worked a bit to make more sense for myself. They still work for the scripts I put them into so hopefully they work for you too.
Download:
https://www.dropbox.com/s/2xb1kyvc1u7d1pj/NameDB.zip?dl=1
Installation instructions:
1a. If you are using mmf: go through the triggers, aliases and scripts and disable/delete the NameDB folders. This step is very important and you will need to do this every time you update mmf.
1b. If you are not using mmf: ensure your profile has gmcp turned on.
2. Restart the profile.
3. Install the package through the package manager.
4. Restart the profile again.
The alias ndbc is more or less what mmconfig politics used to do.
To-do:
-Fix bugs that are certain to exist
-Do stuff with guilds. Maybe show them in CWHO.
-Other things that I wanted to do but forgot about at this time
Credits:
-Vadi for the original ndb which I stole a lot of the stuff from.
-All the contributors who have helped upkeep mmf in general.
9
(c) Iron Realms Entertainment 2012.
Comments
MMF is open source, so anyone who wants to can still "update it," just not going to need someone to keep adding lines / adjusting cures / fixing things.
Standalone scripts are great if you only want a couple of things and do not want the bloat of the entire package, but if you want everything in that package (sans curing) seems like you might as well stick with it...
It is not like it is suddenly going to Just Stop Working.
Guess I'm a bit confused by your question, Kerith.
I don't know how to script much beyond the very basics, myself. That's why I'm grateful other people are doing these things.
Standalone scripts are (again) great for someone who wants completely different behaviour, who does not want the full package, or who wants to test something that might potentially get merged later. The sense I am getting from Falmiis here is that this is the former (wants something he can customize to his preferences entirely without breaking the existing for all MMF users).
Theoretically when it is no longer a beta it could be merged in for all users, but that would be entirely up to him. And if not, you can use his as an override to MMF's default if you like it more-- which may be a compelling reason to leave it separate, giving users that choice.
just do mmignore afflictionname.
== Professional Girl Gamer ==
Yes I play games
Yes I'm a girl
get over it
And you never know, it might work well enough to be a semi-permanent solution. Of course, SSC implementation is a great opportunity to do some cleaning up of my profile and scripts, and rewrite some badly written, oldcode from years ago. It's overdue for spring cleaning.
I figure I'll want to test the server side curing when it comes out asap but from the looks of it the defense thing will be needed.
Also I know it may sound a pain to ignore every affliction but well it took me 5 mins to make a note pad with copy paste. When I'm home form work I'll list it on paste bin so folks can use it in the transtion period if they want to keep the full mm but turn off curing.
Seperating it in the long run seems a good idea but for now while were working out the server side curing, same as anything it may not work right from the get go so I like the idea of having an alias to turn the mm curing on and off to cover stuff in the in between time.
Like I know I have a if attraction function in some of my movement stuff so they'll potentially still be a want or a need for folks to track afflictions system side. Not sure because well we dont know how server side curing is going to work exactly so just guessing.