Another webDip F2F tournament will be held in Marlborough, Ma, USA Aug 22-23. See here for more info.
We get a lot of feature requests. If your feature request isn't already on our issue tracker, then the best place to ask is the forum. This will help us gauge support for your ideas, before we add it to the todo list.
If you're familiar with github, you're welcome to submit a bug report in our issue tracker. Please be as detailed as possible, and include steps to reproduce the bug, what happens, and what you expect to happen instead. If you don't want to use github, you can also email bug reports to email@example.com.
We welcome code contributions for any of the issues on the "soon" milestone. Simply fork the project, and develop a fix in a branch. We accept pull requests that:
When writing the text of your pull request, please include:
Any questions, please email firstname.lastname@example.org, and a member of the dev team will answer.
github.com/kestasjk/webDiplomacy - the code
github.com/kestasjk/webDiplomacy - the issues
README.txt - Installation data for webmasters
AGPL.txt - The license protecting this code, if you make changes to the code you've got to share those changes.
If you want to make a change this is where you should start. The two images and text files below will give you a feel for where everything is and how webDip is structured, so you know where to go to find whatever you need to change.
gotchas.txt - Annoying quirks
archive.txt - Info on the archive tables
coasts.txt - Info on how coasts are handled
We used to have a forum for developers, but it was closed due to inactivity and spammers. Some of the content there is still useful: forum.webdiplomacy.net