Jobs & History

Every custom build is a job with its own number. Each change you ask for on that job is a new revision. The AI keeps track of all of them, so you can always get an older jar back or build something new on top of one.

Reading a jar name

XenoLevels-0.5.6-J51-R2.jar
           │     │   └── revision 2 of that job
           │     └────── job 51
           └──────────── built from XenoLevels 0.5.6

In messages the AI writes the same thing out as Job 51 rev 2.

Asking for changes

Right after a delivery: just describe what you want changed in the same thread, or press Needs tweaks. That becomes the next revision of the same job (Job 51 rev 2, rev 3, ...).
On an older job: mention it, for example "on top of Job 51, add ...". That starts a new job built on top of the earlier one, so the earlier job stays exactly as it was.
From scratch: when the AI offers to build on one of your earlier jobs, pick Start fresh to begin from the latest official version instead.

Your job history

Type !jobs (or just "my jobs") in a help forum to see every job and revision you have received.

Get the jar

Pick a job from the list to have that exact jar sent to you again, for example to go back to an earlier revision.

Build on this

Start a new version from any earlier job or revision. Your next request in that thread builds on it.

Jobs stay with their plugin

You can only reuse a job in its own plugin's forum: XenoLevels jobs in the XenoLevels forum, and so on. Jobs from other plugins are still listed, grayed out, so you can see everything in one place.