@skew
At least some of it had been posted onto a github, but I don't know how public that was meant to be.

@Alzie said:

I would say that being a coder or knowing mushcode does not make you able to modify ajobs. Ajobs is a beast of a thing that doesn't like to be messed with. Even if you do know mushcode and are a veteran coder to boot, Ajobs will chew you up and spit you out. That's how annoying it is. Really, the only people that know Ajobs are those poor souls who for whatever reason bring that soul crushing hell upon themselves willingly and work through the code.

I cut my teeth when I first began coding "seriously" (as seriously as I do anything mu*wise), on features for aJobs.

@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.

@Scorn said in Basic Anomaly +Jobs Functions:

Maybe I'm crazy. I probably am. (Okay, definitely.) But I'm curious.. how difficult would it be to configure the list of displayed jobs (i.e. when you type +jobs) to include the name of the submitting player as well as bucket, job name, due date, assigned, status?

(Ssssh, I'm not supposed to post.)

But this is actually already a function. You just change your &jobs me=<stuff>. For example: &jobs me=BOTD will give you bucket, opened by, title, and date. &jobs me=BOTDS gives bucket, opened by, title, date, status.