Bukkit

[v2.0.0]
    Complete plugin re-vamp!
    Config file has been split; YOU WILL NEED TO DELETE OLD FILE.
    New permissions hierarchy and command system
    All output and sign text has a new color scheme (a.k.a there is color now.)
    Internal code has been re-written
    NEW COMMANDS: Upgrade, Rename
        * Upgrade is /mja only, upgrades player job to server job.
    NEW JOB TYPES: Craft, Smelt, Brew, Enchant
        * Players with a crafting job will NOT be able to shiftclick crafted items out when crafting job items.
    Players can now (optionally) make their own jobs for other people to work on
        (Job payments come from job owner, not server.)
    Signs are updated, they'll work a bit better now.
    !! Problem with tool multipliers that cancelled payout unless tool was listed is FIXED
    !! Jobs no longer work if players are in Creative Mode
    !! Reload command removed, configs automatically reload from disk with every command.
    And probably more than that. I'm terrible at keeping a changelog so I'm writing this from memory...
[v1.2.0]
    Fixed problems with config loading
    Added sign support (Getjob and QuitJob)
    Added an optional maximum to how many people can have a certain job at a time
    Added tool multipliers to jobs
[v1.1.0]
    Fixed exploit where players could get build and place jobs and spam for money.
    '/mj job delete' now removes job from player job list as well as just deleting the job.
    Unnecessarily repetitive chat messages have been removed.
    Added more chat interfaces (Confirmation messages, "You earned ...", errors, etc.)
    Tidied code overall.
[v1.0.3]
    Added alias for '/mj job': '/job'
    Fixed '/mj job addWorld' (and technically '/job addWorld')
[v1.0.2]
    Updated config file with pre-made jobs.
[v1.0.0]
    Brand new~!

Players with a crafting job will NOT be able to shift-click crafted items out when crafting job items.
Sending a non-integer value in a command that's looking for an integer throws an error. I'll be looking for a filter to fix that for 2.0.1 no matter what.
I'm kinda lazy with testing, so there's a chance of other issues...