Bukkit

• With some help of Myaugav and some suggestions from him, remade some parts of how jobs looking in general. I hope you will like it 
• New /jobs browse look to show only job name in short list and by hovering over to see basic information about it

• By clicking on job name new window will popup with more detailed information which will include new FullDescription option

• From where you can check detailed action list, basically same as /jobs info
• Or you can choose job by clicking last line. Which will ask for confirmation by clicking again on confirmation message
• Next. New look for pagination. Which will provide option to scroll throw pages and will show current page and total pages in same line. More cleaner look in overall.

• New look and option to fully customize help page

• Small update for time visualization which could some times result in hours being shown bigger than 24 what should not happen
• Fix for help page popping up when failing to find top and gtop list. Now only error message should appear.
• As of request and necessity to have option like this. Added way to save furnace and brewing stand "owner" and reassign after server restart. This will prevent that annoying thing when you have to re click each furnace/brewing stand to get paid again from them.
• To "battle" previous feature and have some extra control. Now players are limited by default to 20 furnaces and 20 brewing stands from which they can get paid. This can be changed in config file or by giving jobs.maxbrewingstands.[amount] or jobs.maxfurnaces.[amount] you will get action bar message informing how many you have and how many you can place. You can always disable this by setting default max to 0.
• Keep in mind that now you cant take over ownership if furnace already belongs to some one else. So first clicked will be owner and will get money for smelting if he is in appropriate job.
• Added new command for previous ownership feature to clear out any registered furnaces or brewing stands if you cant remember which are yours or where they are and you want to register new ones in new place to be under limit /jobs clearownership (playerName) where only players with jobs.command.admin.clearownership can use command on others
• Added option to remove particular amount of percentage from level when player leaves job at max level. This will allow to have different level loss when player leaves job with max level. Keep in mind that fix-at-max-level should be set to false for it to have effect.

Now last and most interesting part 

• As of Myaugav suggestion and some help out with general idea. Added daily quests.

• Now each job can have unlimited amount of quests player can complete to get rewards.
• Example quest setup looks like this

    # Defines maximum amount of daily quests player can have from THIS job
    # This will not have effect on overall quest amount player will have
    maxDailyQuests: 3
    # Daily quests
    # Each job can have as many daily quests as you want
    # Players will have access to quests from jobs he is currently working at
    Quests:
      # Quest identification. Can be any ONE word or number or both of them. This doesnt have any real meaning but it cant repeat
      1:
        # Quest name used for quests list, don't forget to enclose it with " "
        Name: "Break Oak wood"
        # Quest action can be any valid job action. Look at lower for all possible action types
        Action: Break
        # Target id or name. Comes in same format as it is for regular job action
        Target: "17-0"
        # Amount of actions players should perform to complete this quest
        Amount: 300
        # Command list to be performed after quest is finished.
        # Use [playerName] to insert players name who finished that quest
        RewardCommands: 
        - "money give [playerName] 500"
        - "msg [playerName] Completed quest!"
        # Quest description to be used to explain quest requirements or rewards for player
        RewardDesc: 
        - "Break 300 Oak wood"
        - "Get 500 bucks for this"
        # Defines chance in getting this quest. 
        # If you have set 10 quests and player can have only 2, then quests with biggest chance will be picked most likely
        # This will allow to have some rare quests with legendary rewards
        Chance: 40
        # Defines to which job level you want to give out this quest. 
        # Keep in mind that player will keep quest even if he is over level limit if he got new one while being under
        # In example: player with level 2 takes quests and levels up to level 5, he still can finish this quest and after next quest reset (check general config file) he will no longer have option to get this quest
        toLevel: 3
        # Defines from which level you want to give option to get this quest
        # You can use both limitations to have limited quests for particular job level ranges
        fromLevel: 5
      2:
        Name: "Zombie killer"
        Action: Kill
        Target: Zombie
        Amount: 50
        RewardCommands: 
        - "money give [playerName] 2000"
        - "msg [playerName] Completed quest!"
        RewardDesc: 
        - "Kill 50 zombies"
        - "Get 2000 for this!"
      3:
        Name: "Chicken cooker"
        Action: Smelt
        Target: "COOKED_CHICKEN"
        Amount: 20
        RewardCommands: 
        - "money give [playerName] 300"
        - "msg [playerName] Completed quest!"
        RewardDesc: 
        - "Cook some chicken breasts"
        - "Get 300 for this!"

• Its more or less self explanatory and well comments does that too 
• Each job have its own max daily quest limit. so you can give one random quest each day for players to complete.
• Quest actions are not limited to particular job, so miner can have quest to cook some chicken
• New command to check currently outgoing quests for player /jobs quests (playerName) where again, only players with jobs.command.admin.quests can check another player quest progression

• You will get information about available quests,  with its name and progression bar
• Completed quests will be marked as completed, just for simplicity sake
• Number near name will indicate how many daily quests you did in overall. This will be utilized in future for additional features.
• By default quests will reset at 4:00 at night which will be indicated by timer when hovering over quest.
• Keep in mind! For now daily quest progression is not gonna be saved into data base, so server restart will result in quest reset. Will have to work on that at some point.