Basic Anomaly +Jobs Functions


  • Tutorialist

    (This is a work in progress, I'll add to this over the next few days as I get time. I hope that is alright, @Glitch.)

    First Things First! How do I /get/ Anomaly +Jobs?!

    ** I highly recommend you have installed myrddin's +Bbs first. It can be found at this webpaget. Just c/p paste the code into your mush client, and let it run.

    Go to the Anomaly Jobs Google Hub, click on "downloads", download the latest version of AnomJobs. Unzip the folder, and open the AnomJobs text file, and c/p paste all everything into the folder into your client (using a wizbit), and let it go. It'll be a little while. Yay! Now you have AnomJobs installed! You may have a few new objects int your inventory (check with 'i' or 'inv'), if you do you'll want to @tel them to your master room (this is typically #2). (@tel jgo=#2, etc)

    Great! Now what?

    Now you can begin using your +jobs!

    But how??

    There are various controls for basic use of AnomJobs. They start with:

    • +jobs
    • +jobs/mine
    • +job #
    • +job/add #=<things>
    • +job/mail #=<things>
    • +job/approve #=<Things>
    • +job/deny #=<things>
    • +job/complete #=<things>
    • +job/merge #=#
    • +job/trans #=<bucket>

    What does '+Jobs' do? (Or how do I see all of the +jobs?)

    +jobs is the command you use when you want to see all of the jobs (in the buckets you subscribe to). The typical display will look something like this:

    =======================================| Anomaly Jobs v6.5 |=======================================
    *  Job# Type  Title                                              Due On   Assigned To      Status
     ---------------------------------------------------------------------------------------------------
       1 MUSE  Things Forgotten                                   -------- Cobalt             NEW
       2 CODE  Sigsev error                                       -------- Thenomain          NEW
       3 CODE  Note Code                                          --HOLD-- Thenomain        --HOLD--
       4 MUSE  Muse intro                                         -------- -                  NEW
       5 CODE  Total Succs on Extended                            -------- Thenomain          NEW
       6 CODE  +sheet/show specific items                         -------- Thenomain          NEW
       7 CODE  BUG: @tel & Not approved                           --HOLD-- Thenomain        --HOLD--
       8 CODE  FEEP: +events improvs                              -------- CobaltCode         NEW
       9 CODE  BUG: Specialty check for wolfbloode                --HOLD-- Thenomain        --HOLD--
      10 CODE  BUG: Sub-Templates                                 --HOLD-- Thenomain        --HOLD--
      11 CODE  +templte/change                                    -------- Thenomain          NEW
      12 CODE  +poll                                              -------- CobaltCode         NEW
      13 CODE  +loginreport                                       -------- CobaltCode         NEW
    * 14 CODE  /booster roll switch                               -------- Thenomain          NEW
     ====================================| * Denotes New Activity |=====================================
    

    The first column will have an asteric (*) if there is new activity on the job.

    The second gives you the job number. Jobs are internally organized by their 'number'. To do anything with a job you need to use it's number.

    The third column tells you what bucket it is in-- general request is REQ, you can define buckets (we'll talk about that later).

    The third column tells you the name of the job.

    The forth tells you it's due date.

    And the fifth tells you who it is assigned to.

    You can change the layout of how this looks, btw. But I'll cover that a little bit later.

    What does +jobs/mine do? (Or how do I see just my +jobs?)

    To see jobs that are only assigned (or tagged) to you, type in +jobs/mine. This will give you a list that is formatted exactly like the one from +jobs, but will show only +jobs that are assigned to you, or have you tagged to them.

    =======================================| Anomaly Jobs v6.5 |=======================================
     *  Job# Type  Title                                              Due On   Assigned To      Status
    ---------------------------------------------------------------------------------------------------
        1 MUSE  Things Forgotten                                   -------- Cobalt             NEW
       22 CODE  +travel                                            -------- Cobalt             NEW
    ====================================| * Denotes New Activity |=====================================
    

    What does 'tagging' mean on a +job?

    You may be tagged on a job at some point. This means that someone has used: +job/tag #=You! The job will show up in your +jobs/mine list, however, it will leave this list (untag itself) as soon as you comment on the job in some manner (either via +job/add or +job/mail).

    What does '+job #' do? (Or how do I view a specific +job?)

    Okay! You know what +jobs you need to do! How do you read them to figure out what they are about? (I mean, you can tell from the title that whoever requested +job #1 wants pie, but what if they want a specific type of pie?)

    You would type: +job #
    So : +job 1

    ==========================================| View Job 22 |==========================================
     Bucket: CODE                                        Due On: -
     Title: +travel                                     Status: Green (New)
     Opened On: Tue Dec 17 21:40:09 2013               Assigned To: Cobalt
     Opened By: Cobalt
     ---------------------------------------------------------------------------------------------------
    [1+] Cobalt added on Tue Dec 17 21:40:09 2013: We need it.
     ---------------------------------------------------------------------------------------------------
    [3+] Cobalt added on Sun Mar 30 01:21:42 2014: +TRAVEL CODE FRAMEWORK - COBALT'S +TRAVEL 1.0
    (( I removed a bunch of noise from here, but here you can see another comment added to the +job.))
    
     ===========================================| [Myjobs] |============================================
    

    The header tells you the +job number, and then the banner will tell you

    • Bucket
      *Title
    • When the job was opened.
    • Who opened the job.
    • When it is due -- if there is no due date it just has -.
    • Status (this is different with different jobs setup. Sometimes it's 'green, red, yellow' sometimes its 'withplayer, staff'. Check with other members of your staff.)
    • And then who it is assigned to.

    After the manner, you will have the comments. Every comment will have a number next to it with either a + or -. A - next to the comment number means that the person who opened the job CANNOT see that comment. A + next to the comment number means that the person who opened the job CAN see the comment.

    You will note that the comment number seems to jump. This is because anything you do to the job is assigned a number and is tracked internally in the job (we'll look at how to see that later on). So if you +job/assign ##=Cobalt -- the act of assigning the job is given a number.

    What does '+jobs/add' do? (Or how do I make staff only comments?)

    If you want to make a comment on a job, but DO NOT want non-staff to see it, you should use: +job/add #=<comments.

    +job/add 43=I really like this idea, but I am not certain it works within our theme.  
    Maybe we could ask the player to tweak it a little bit?  
    Perhaps she could *think* she is a pixie-faerie rather than actually is one?
    

    This will leave a comment on the job that only other staff members (or players with special privileges can see, but we'll discuss special privs when we discuss buckets).

    What does '+job/mail' do? (Or how do I communicate with a player in the job, without closing it?)

    If you want to make a comment, or talk to the player, inside of the +job and want to keep the +job open you should use +job/mail #=<comments>.

    +job/mail 43=Hey, @EmmahSue!  I really like your idea of being a pixie-faerie with the 
    kleptomania flaw!  Your character sounds really cool.  However, we don't have a 'pixie-faerie'
    template on our game.  Perhaps your character could have another flaw?  Delusions (Pixie-Faerie)?
    

    This will send an @mail to the player with the above comments, and will also leave the comments inside of the job visible to the player and other members of staff.

    What does '+job/approve' do? (Or how do I close a +job part 1?)

    There are several different ways to close a job. The most used one +job/approve #=<comments>. This will close a +job and if you have myrddin's bbs installed it will post the original body of the job, and your closing comments, onto a staff only bbs, and well as @mail the player with your closing comments.

    +job/approve 1=Sure, @Thenomain, you can have some pie!  RIGHT TO THE FACE!
    

    This will send Thenomain an @mail saying: 'Sure, Thenomain, you can have pie! RIGHT TO THE FACE!'.

    What does '+job/deny #=' do? (Or how do I close a +job part 2?)

    So you want to tell a player "no". Or close a job out on the negatory. You will want to do +job/deny #=<comments>. Like +job/approve if you have a bbs tracker it will post to the denied board, and @mail the player letting them know.

    +job/deny 1=No, @Thenomain, you may not have pie.
    

    What does +job/complete do? (Or how do I close a +job part 2?)

    So there is a third option to close jobs. This one will NOT @mail the player, and if you have myrddin's bbs set up will post to a PUBLIC board. Typically this is meant for +jobs that are closed that everyone should be aware of. Code change, grid changes, policy changes. Etc. You should probably never +job/complete a job a player put in. But say you make a big change to the grid and you want everyone to know that the project is done, you can do:

     +job/complete 1=Everyone gets pie!
    

    This will post to the public board (if you have myrddin's bbs set up, if you don't the job will just disappear) for everyone to see.

    What does +job/delete do? (Or how to close a job, finale~)

    There is one last way to close out a job. This command just makes the +job go away. It won't @mail the player, won't post to a BBS, and doesn't make any announcements to people. It is +job/delete.

     +job/delete 1
    

    That's it, that's all you have to type. No comments, no words, justs +job/delete #1.

    What does +job/merge do? (Or how to smoosh jobs together.)

    So you have two jobs that are basically the same thing? (This is typically bug reports, etc.) Instead of dealing with two +jobs you can smoosh them together in one +job. To do this you do:

     +job/merge 1=2.
    

    This will merge +job 1 into +job 2. So you will see the contents of +job 1 after the contents of +job 1.
    To be continued! I need catch my bus now. :}

    What does '+job/trans #=Bucket' do? (Or how to move a job from one bucket to another.)

    So someone put soething in as a +Request, but it needs to be in code or build or in their sphere bucket? How do you move it? Simple! +job/trans! Just do:

     +job/trans 1=Pie
    

    This will move the request from the REQ bucket into the 'Pie' bucket. As a ''NOTE'' this is a good way to save a +job if you've oopsed, and closed the wrong +job. Or accidentally closed a +job when you didn't mean to. You don't have a lot of time, but if you catch it quickly you can +job/trans 1=REQ, and it will keep the +job from disappearing.

    throws down a smokebomb, bamf!


  • Coder

    @Cobaltasaurus Works in progress are great and thanks for taking the time to do this one!


  • Tutorialist

    Need to edit all those codey bits, they look awful! Bad examples. Will fix later!


  • Tutorialist

    Okay, so some very very basic functions are listed. I think we I get more time I'm going to go through, and try to figure out how to link to specific comments. So you can click on the topic you want, and it'll scroll you down to that specific command. Rather than having to scroll through the entire thing.

    But does anyone have any questions so far? @Bobotron is this good, or too basic? Next I'll talk about buckets, and maybe some configurations.



  • @Cobaltasaurus said:

    Okay, so some very very basic functions are listed. I think we I get more time I'm going to go through, and try to figure out how to link to specific comments. So you can click on the topic you want, and it'll scroll you down to that specific command. Rather than having to scroll through the entire thing.

    But does anyone have any questions so far? @Bobotron is this good, or too basic? Next I'll talk about buckets, and maybe some configurations.

    Nah, this is pretty good. It is simple, but sometimes simpler is better. Seeing it all in action makes it work much better in my head.



  • 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?


  • Tutorialist

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


Log in to reply
 

Looks like your connection to MU Soapbox was lost, please wait while we try to reconnect.