[REJECTED] moderation tickets

[Wundsalz]

I've seen alot of guests asking for a review over and over again lately. They often fail to draw attention to their builds at all (a good example is juan, who applied in the forum after trying for over an hour to get a review ingame). This problem gets fortified by a lack of OPs during some periods of time. Similar situations can occur whereever a player has to rely on a higher ranks commands.
As such situations are frustrating for the new players and should be avoided, I suggest to introduce a ticket system to work off guest requests. In Additon the system can be used to create another e-pen stat for our moderators
I'll try to outline the system I have in mind:

ticket class
variables:
PLAYER contains information who has created the ticket
TYPE possible values: review, copy, water, lava, grass, grief, spleef, worldcreation, other
MARK class containing information about the world, coordinates and viewangle of the requesting player
COMPub a public comment string allowing the requester to expatiate his request
COMMod a string readable and writeable by higher ranks only. E.g. It can be useful if there's a lack of moderators for promotions. This way a single OP can review a building and write his opinion into the string viewable by other OPs. This can allow promotions without multiple OPs beeing online at the same time. It can also be usefull for builders and vets to tell that they've taken a water/copy job.
ID request ID
CREATIONTIME contains information when the ticket was created
MARKRight who is allowed to set MARKs? can be TYPE- and Rankspecific. Creating Player should alway be allowed to edit his MARKs
COMPubRight who is allowed to edit the public comment string? can be TYPE- and Rankspecific. Creating Player should alway be allowed to edit his MARKs
COMModRight who is allowed to edit the moderation comment string? can be TYPE- and Rankspecific

some possible commands for this system:
/createticket TYPE COMPub
- creates a ticket, setting PLAYER, TYPE, MARK and COMPub, CREATIONTIME, COMPubRight, COMModRight and ID
- a chat msg can be sent to inform TYPE-specific ranks about the ticket creation (eg water requests could be displayed to builder+, grief/spleef to vet+ and review requests can be displayed to OP+)
/ticket ID
- displays ticket information (PLAYER TYPE MARK COMPub and COMMod (check rank))
/ticket PLAYER
- display tickets created by PLAYER (maybe with a brief information)
- if there is only one ticket run /ticket ID instead
/COMPubSet PLAYER/ID MESSAGE
- sets the public comment
/COMPubAdd PLAYER/ID MESSAGE
- adds text to the existing public comment
/COMModSet PLAYER/ID MESSAGE
- sets the moderation comment
/COMModAdd PLAYER/ID MESSAGE
- adds text to the existing moderation comment
/MARKSet PLAYER/ID and/or /MARK PLAYER/ID
/ticketdelete ID
- deletes ticket
/ticketdeleteall PLAYER
- deletes all tickets by player
/ticketdeleteold CREATIONTIME
- deletes tickets which have been created before CREATIONTIME
/ticket
- displays the latest request/rank specific tickets
/ticketdone
- delete ticket/mark it as worked off
- mod-e-pen-stat +1

[Lim-Dul]

Much, much too specific and complicated. fCraft focuses on simplicity. Everybody would like to have moderation tickets implemented differently and probably integrated with a DB of some sorts, which makes this feature not too appealing to the general public while requiring a lot of coding.
I think the best course of action here is to simply modify the software to your needs - I don't know how functional the API is at the moment.

[fragmer]

I appreciate all the thought put into your suggestion, but I have to reject it. This will be possible to do with mods or plugins, when fCraft's plugin system is done. It's too complex and specialized to add into the fCraft core.