v0.4.0

Details

  • Filename
    ReportRTS.jar
  • Uploaded by
  • Uploaded
    Jun 1, 2012
  • Size
    60.87 KB
  • Downloads
    1,186
  • MD5
    d96cf804aae6fcfcceec55f9976da23a

Supported Bukkit Versions

  • CB 1.2.5-R3.0

Changelog

IF YOU ARE RUNNING SQLITE AND HAS BEEN RUNNING THIS PLUGIN PRIOR TO VERSION 0.4.0 YOU NEED TO DO ONE OF THESE TWO THINGS:
1. Delete your old ReportRTS.db file before starting the server with ReportRTS v0.4.0
2. Start ReportRTS v0.4.0 (it WILL cause errors to occur, worry not!), then once fully started, as OP run /reportrts upgrade. Once this completes, run /reportrts reload and everything should be okay.

  • Help signs will no longer pop off the ground without a error message.
  • Performing /check on closed tickets will now display the comment (if any) that the staff member made.
  • Claiming is no longer just a visual thing, only players with the permission reportrts.override can override a ticket.
  • Falling back onto SQLite when a MySQL connection fails is working again.
  • Closed tickets can no longer be put on hold.
  • You can now check your latest closed tickets by typing /check closed, this is ordered by latest closed. Read from top to bottom.
  • Better debug mode. Now provides some more information for those of you who do not log all commands on a server.
  • Save yaw and pitch when filing tickets. This means that when you /tp-id to your ticket, you will now also look where the person who made the ticket was looking.
  • The amount of requests shown per page is now configurable.
  • ModTRS import feature removed, we are no longer going to hold the plugin back by keeping it backwards compatible.
  • Fix an issue that occured in one of the development builds where any /reportrts command that interacted with the database failed.
  • When doing /check on a closed ticket, the time spent on the ticket (from when it was filed, to when it was closed) is shown.
  • When doing /check on a claimed ticket, the amount of time that the ticket has been claimed is shown.
  • Added a absolutely 100% necessary /reportrts upgrade (only available for OP) command for ALL SQLite users that has been using this plugin before v0.4.0. THIS IS A NECESSARY STEP TO GO THROUGH BECAUSE OF A BUG.

0.3.3

  • Add missing permission node for import. reportrts.command.import, defaults to false so it has to be specified for the OP's group.
  • Stop empty help signs from being created.
  • Built against CB 1.2.5-R1.0
  • Fixed debug mode not triggering on all types of /check commands.
  • Option to hide requests from /check if the user who filed the request is offline. NEW
  • Cancellation System! Let users cancel their own requests by typing /complete id, it works similar to /check, permission node reportrts.command.complete.self NEW
  • Fix a error that occurred when a user logged in that had a pending notification after the database has been reset.

0.3.2

  • Added assigned ticket ID to message modreqFiledMod. REGENERATION IS NEEDED, remove the line with "modreqFiledMod" from messages in config.yml.
  • Configurable delay for filing modreqs, stop those spammers.
  • Moved maxRequests to request.max to clean up the configuration a little (old maxRequest limit will be ignored! Make sure you set the new max in the section called "request", default is 5.
  • Very experimental and probably broken ModTRS (MySQL only, so far) importer added. /reportrts import (node needed: reportrts.command.import)
  • Fixed a bug with help signs trimming whitespace from linebreaks.
  • Fixed a bug with help signs not reporting the ticket ID assigned.
  • Added debug mode back. Disabled by default, you can enable it in the configuration by setting debug: true.
  • Added limited stats tracking for individual players. /reportrts stats <player>, permission node needed: reportrts.command.stats

IF YOU ARE RUNNING SQLITE AND HAS BEEN RUNNING THIS PLUGIN PRIOR TO VERSION 0.4.0 YOU NEED TO DO ONE OF THESE TWO THINGS:


  1. Delete your old ReportRTS.db file before starting the server with ReportRTS v0.4.0
  2. Start ReportRTS v0.4.0 (it WILL cause errors to occur, worry not!), then once fully started, as OP run /reportrts upgrade. Once this completes, run /reportrts reload and everything should be okay.