Jobs Reborn

To install Jobs Reborn, you must also include the CMILib library in your server's plugins directory. Follow these steps:

1. Stop your server using the /stop command.
2. Download the latest CMILib.jar and place it in the ~/plugins/ directory.
3. Download the latest Jobs-Reborn.jar and place it in the ~/plugins/ directory.
4. Start your server.
5. Once the server has finished loading (the 'Done!' message appears), the plugin will have generated its configuration and language files.
6. Stop and restart the server again to begin customizing settings like jobs, economy, and chat.

# Ensure both jars are in the plugins folder
~/plugins/CMILib.jar
~/plugins/Jobs-Reborn.jar

The plugin provides mechanisms to view detailed information about jobs and player progression:

• Job Info: Displays details about a job, including income (Money), experience (EXP), and points for specific materials/actions. This can be filtered by ActionType (e.g., mining, woodcutting).
• Job Stats: Displays a player's current level, experience, and a progress bar towards the next level.
• Player Info: Allows viewing the job status and progression of other players.

To allow a player to join a specific job, they must have the following permissions:

1. jobs.use (General permission to use the plugin)
2. jobs.join.<jobname> (Specific permission for the job, where <jobname> is the lowercase name of the job).

Example for a 'Miner' job:

• jobs.use
• jobs.join.miner

The /jobs command is the primary entrypoint for interacting with the Jobs plugin. It supports various subcommands for managing jobs, viewing player information, and checking job statistics.

General Usage:

• /jobs or /jobs help: Displays the help menu. You can specify a page number (e.g., /jobs help 2) to browse through available commands.
• /jobs <command> [arguments]: Executes a specific subcommand.
• /jobs <command> [arguments] ?: Displays the usage instructions for a specific subcommand.

Permissions:

• Most commands require the permission jobs.command.<subcommand>.
• Access to specific jobs is controlled via jobs.join.<jobname>.
• General job usage requires jobs.use.

/jobs help
/jobs help 2
/jobs <subcommand> [args]
/jobs <subcommand> [args] ?

The command supports pagination and an optional action parameter.

Usage Pattern:

1. /editquests [page] - Lists quests starting from the specified page.
2. /editquests [page] list - Explicitly lists quests (defaults to list if no action is provided).

Once a quest is selected from the list, an interactive 'Main Window' opens in chat. You can click on different parts of the message to edit specific quest attributes.

# Example: List quests starting from page 1
/editquests 1

When editing a quest via the interactive menu, clicking on specific text elements allows you to change the following attributes:

• Name: Change the display name of the quest.
• Job: Reassign the quest to a different job.
• Chance: Set the spawn probability (0-100).
• Reward Amount: Set the numerical reward value.
• Enabled: Toggle the quest on or off.
• Level Range: Set the minimum (from) and maximum (to) player levels required.
• Objectives: Edit the list of requirements for the quest.
• Rewards: Edit the commands executed upon quest completion.
• Description: Edit the quest's description text.
• Restricted Areas: Edit areas where the quest cannot be performed.

To use the Jobs API in your Gradle project, add the JitPack repository and implement the Jobs dependency.

repositories {
    maven {
        url 'https://jitpack.io'
    }
}

dependencies {
    implementation 'com.github.Zrips:Jobs:v5.2.6.2'
}

To use the Jobs API in your Maven project, add the JitPack repository and the Jobs dependency. Note that the scope should be provided as the plugin will be present on the server at runtime.

<repositories>
    <repository>
        <id>jitpack.io</id>
        <url>https://jitpack.io</url>
    </repository>
</repositories>

<dependencies>
    <dependency>
        <groupId>com.github.Zrips</groupId>
        <artifactId>Jobs</artifactId>
        <version>v5.2.6.2</version>
        <scope>provided</scope>
    </dependency>
</dependencies>

You can use the reset flag with the boost command to clear multipliers. The scope of the reset depends on the arguments provided:

• Reset everything: boost reset resets all currency boosts for all jobs to 0.
• Reset all currency types for all jobs: boost reset [type] resets the specified currency boost for all jobs.
• Reset all currency types for one job: boost reset [job] resets all currency boosts for that specific job.
• Reset a specific currency for one job: boost reset [job] [type] resets only the specified currency boost for the specified job.

# Examples of reset commands (conceptual)
/boost reset
/boost reset MONEY
/boost reset Miner
/boost reset Miner MONEY

To view statistics for other players, the user must possess the following permission:

• jobs.command.admin.stats: Required to use /jobs stats <player> to view another player's job data.

The jobs browse command supports the following flags to modify the output:

jobs browse -p:1
jobs browse -j:Miner