Petition system
 

ok guys i need to talk realtime to a dev who knows how the petition system works

/petition <message> - Creates a petition and adds it to the queue

#listpetition - lists all open petitions that haven't been deleted

#viewpetition <number> - views the petition number found in the output of the #listpetition command. This will show the message entered by the petitioner.

#delpetition <number> - deletes the petition

That is about all there is to it. I know you requested a dev, but I am not sure what else you could possibly want to know about it unless you are changing code to get the UI petition system working.

i mean internally for my gui i need to know more about the system as to what aspects are required and what arent by the database and so forth in order to make the petition manager

i also need to know what the fields for unavailables are for for instance

The only field in that table (from the copy I'm looking at) that is not required on INSERT is `gmtext` (because there wouldn't be any gmtext when the player first submits a ticket).

The structure also saves things like the level of urgency -- GMs/Guides can raise or lower an escalation level of the petition, checkouts -- should be a count of how many times the petition has been looked at with the in-game UI, lastgm -- name of the last person to have looked at the petition, etc.

Edit: I meant to include: unavailable is probably going to be the count of how many times a GM checked out the petition but the player wasn't around to respond.

yeah that was my thinking actually thanks i got the petition manager working in its most basic form