Haunted Memories Anomaly Jobs Customizations
-
So I'm in the process of cleaning up my SQL Bulletin Boards, but while I was at it I remembered that HM had a lot of custom AJobs modifications that people really seemed to quite like. Almost all of those modifications were stored on one object (#49) which was stored in the Master Room and @parented to the actual Anomaly Jobs Command Object. In turn, the Anomaly Jobs Command Object was stored in that object's inventory, thus allowing us to modify the heck out of AJobs without ever modifying the underlying sourcecode. This made upgrades really seamless.
This code is Unlicensed. Please enjoy.
https://github.com/kkragenbrink/haunted-memories-ajobs-customization
-
People on my fork (TheReach, DarkSpires, Wildcard, most mechanipus people by default, etc.) will find a very relevant mux patch:
https://github.com/lashtear/tinymux/commit/6b19bbb955921265c7f79195f870f466f37c95b1
Which lets us do the same thing on Muxen instead of RHost, if that's your flavor of choice. (Brazil's fork still has that disabled for reasons of taste, I think).
This is definitely my recommended way of applying patches to mush code:
@createnew object,@parentit to the old one, override attributes as needed and put the child in the master room (or zone master room, or whatever). Then further updates to the upstream-controlled object can proceed without directly damaging local house-customizations.Now if only we could find a good way to explain what this all means to the typical mush user...
It is by will alone I set my mind in motion. It is by the juice of Coffea arabica that thoughts acquire speed, the table acquires stains, the stains become a warning. It is by will alone I set my mind in motion.
-
@Chime said:
Now if only we could find a good way to explain what this all means to the typical mush user...
"Zhu Li, do the thing!" (Korra humor.)
edit: Get the coders to go with it first. You know how we love to code in production.
