Table of Contents
There is no support. GgrTF development has been in maintenance mode for several years. You can still report bugs via tells or e-mail, but do not expect that they will be necessarily acted upon.
Take your time to think while writing, and before submitting your report. Good rule of thumb is to include all information that you think might be relevant, but no more than that!
Remember to include information about your system and environment, (*NIX/Linux/Windows), version of TinyFugue ("/ver" command in TF), and version of GgrTF ("/gver" command).
We do not provide support for usage, please refer to the user's manual and only in case the issue is not documented, you might be eligible to ask about it.
Neither we provide technical support for extending GgrTF, nor documentation of the internals. You'll have to figure out the workings yourself.
Be ready to be contacted by developers, in case help and/or more information is required with debugging your issue(s).
Remember not to bother the developers via tells too much, we want to play the game too, instead of just answering your questions and resolving problems.
If you have prepared a fix for some bug or a new feature, you can send us a patch. A changeset patch made against current Mercurial repository head/tip is highly preferred, short instructions on how to do that can be found below. You will probably need to refer to Mercurial guide for generic Mercurial usage instructions and how to set it up. For making proper commits, you'll need to at the very least set up your username, etc.
# 1) Make changes to files $EDITOR ggrtf.tf # 2) Commit related changes to a changeset your local repository hg ci [filenames of changed files or nothing, if you wish to commit everything] # 3) Repeat steps 1 to 2 until satisfied # 4) Export your local changes to a bundle hg bundle mychanges.bz2 https://tnsp.org/hg/batmud/ggrtf/ # 5) Send mychanges.bz2 to us (Ggr), as e-mail attachment ccr@tnsp.org