Github <=> EQ #issue system
 

So, I figured I'd see if anyone else digs this, I'm using it on my rebuildeq server that's coming up.

Note: This requires source code changes. If you're not able to maintain a fork of the source, this is probably too complex for you.

All the instructions are on the github repo: https://github.com/Xackery/githubeq.


To give a quick rundown.. This adds an #issue command. The issue command is similar to #report or /report (but does not replace the old ones yet), and is made where it will create a github issue and sync it within game to give the player some feedback of how GMs are handling the issue. When the #issue is invoked it will report: If a player has an item on their cursor (the item id and name), if the player has a target (PC or NPC), and generic info shown in the detail page picture below.


pictures?
Add in game commands like this:
http://i.imgur.com/blOKa6n.png

That you can manage at github like this:
http://i.imgur.com/oxxs9uN.png

And get details like this:

http://i.imgur.com/HgksxNZ.png


Once closed, or managed via github, it will re-sync in game and let the player know it's been addressed!

Enjoy.

This is sweet man!


Celestial

Oops. I did a minor patch to this (Accidentally posted on wrong topic), adding classes/zone names.
I'll be looking at making this support /petition and /report commands, and also possibly work with the telnet interface.

This tool is now discontinued, I will be working on approaching it a new way in the near future.

If you use this, please let me know if you're interested on the update, that feedback helps me prioritize..

Thanks!

Edit, oh nevermind, haha

It still fully works. What I mean by discontinued is, it doesn't work unless you update the code with uleat's new inventory system tweaks, and the way I store and manage the data is planned to be rewritten so heavily, I figured it's easier to discontinue and move it later.

So, it's still fully usable just need to have a bit of knowledge, but over time, it'll become less and less usable, and I don't plan to maintain it.

Sorry about that..