...aaand it's mailing fine so long as the person who opened the job isn't my cobalt bit. I wonder if the code won't let you @mail yourself on a job, or if its something to do with cobalt owning the code...
Honestly if your wanting to do a fallout or apocalyptic themed game you may want to look into the DSS system. It would allow for what your wanting and have a nice clean look to it with little actual code-fu knowledge to make work. It might be your best option rather than trying to modify a D20 style code base.
@Tat has done this on XF (feeding into @faraday's +cookie system) because she fell in love with the +comp system on the now-defunct Second Pass. Where it was, indeed, just a way to leave nice notes for other players and let them see them after the fact.
Tat can talk more specifically about it if she ever wanders back, but basically every character gets a Comp object and all the comps for a player are stored there. Of course, I know there are limits for how many attributes a single object can hold, so I guess some day we may run into that.
It's very pretty-- but it's a perfect example of what I was trying to avoid. I've been a UNIX person since 1995. I really do want just bare autoconf so that I can automate and do CI testing more easily.
Well, that's the brilliant part of it. It makes a dynamic file called 'custom.defs' in the src directory that has the Makefile variables. So you could use CLI and generate it in a batch or on the fly just fine. The menu is just an interface to generate the custom.defs file, that's it.
Unix guy here since 1985 (AT&T SYS3/SYSV on a 3B2), so I am all for the mighty CLI ;)
That said-- it is really nice to have all of those configurable features. Ideally they should become config options in the game conf file rather than compile-time features, but I understand quite well how big a pain that is.
Yup, we have a ton of customizations that way. All the mysql is in a rhost_mysql.conf, again, the Makefile menu interfaces with it.
The only compile times are those that make huge differences in the code itself, and again is just populated as DEFS's in the custom.defs file. So entirely CLI capable with batch processing. Yay is the UNIX.
Admittedly, a lot of my customizations to MUX were to remove a lot of #ifdefs for obsolete crap.
Take your MUX inc()/dec() option. What's the harm in having that always enabled?
Yea, some of these things we likely will re-visit to change from compile time to just conf parameters, most of it however was due to speed/performance considerations at the time.
[X] 26. SHA512 Passwords
I hope those are still salted?
Absolutely. 10 character randomized seeding per password encryption.
No rainbow table decryption for our baby ;)