1.1.0 ~reboot
@@ ========================================================================
@@ .:....1....:....2....:....3....:....4....:....5....:....6....:....7....:
@@ ------------------------------------------------------------------------
@@ WARPED ~~~~~~~~~~~~~~~~ ~
@@ ~~~~~~~~~ ~~~~~~~~~ WARPEDcore ~~
@@ ~~~~~~ ~~~~~~ ~reboot ~~~
@@ ~~~~ Adoption ~~~~ 200609250b ~~~~
@@ ~~~ Date ~~~~~~ ~~~~~~
@@ ~~ 2006.09.25 ~~~~~~~~~ ~~~~~~~~~
@@ ~ ~~~~~~~~~~~~~~~~ core
@@ ------------------------------------------------------------------------
@@ .:....1....:....2....:....3....:....4....:....5....:....6....:....7....:
@@ ========================================================================
- Printer-friendly version
- Login or register to post comments
Click 
Things I'd like to see...
This may or may not have been the best way to present this (or any other) contribution, but it's the way I did it. Comments on improvements to this methodology are welcome.
Man, it was late when I posted this last night.
Okay. This package is pretty significant in its own right. At the time that I was writing it, I encountered a small obstacle in finding a way to confirm that #1/startup (ALL OF IT) got processed before anyone else's startup. At first, I attempted to write a pseudo-startup (to replace @startup), for all players. This became clunky. And, after some discussion with Javelin (who discussed it with Talek), some changes were made to the hardcode to ensure that god gets a special 'first queue cycle' (I don't remember the details, as I'm not a hardcode person, per se). This code was written specifically to embrace that feature of Pennmush.
Therefore, I'd like to see this module get through this evaluation process as quickly as possible. So, get those brain muscles flexing, gang... Let's get this piece of code out there in the 'official' category ASAP.
Contorting my brain...
In the above code, I am considering changing the attribute names on #1 as follows...
&CONF.~REBOOT_DBREF will become simply &~REBOOT (it'll still simply contain the #dbref of the ~reboot object). This will allow shortening of the code somewhat.
&NOTE.~REBOOT_DBREF will become &~REBOOT.NOTE (content unchanged).
Additionally, I think it's probably operationally safe and appropriate to move &CONF.GROUP_SEQUENCE (and the associated NOTE attrib) over to the ~reboot object, since #1/~reboot can be used to identify where to get that data.
Comments?
Additional Credits
Thanks to Mike@M*U*S*H for putting up with me while I figured out what I was doing 3 years ago when I wrote this code.
NOTICE: Significant rewrite completed.
I've just completed a significant rewrite of this code. It is more efficient in design, although a tiny bit less 'human language' oriented. Attribute names have been shortened, and the 'group names' have been removed altogether (although the functionality of that concept was retained).
For those of you old enough to remember BASIC, it's basically (pun intended) that.
-T