Community forums are a great way to mingle with other level designers using GtkRadiant. They offer general level design tips and help, while providing discussions on works-in-progress, inspiration and the occasional level design contest. Just make sure you abide by general forum etiquette rules.
- Quake3World Level Editing and Modeling
- Quake3World is the official forum for Quake 3 Arena, and contains one of the more popular level design communities. Members are mostly centered on Quake 3 Arena and Quake Live level design using GtkRadiant, but topics can vary with works from other mods and engines. User beware if you venture outside of LEM, it's a very different crowd.
- Splash Damage Forums
- Splash Damage is a game studio known for shipping some triple-A titles. Their forum caters to games created by the company, including Return to Castle Wolfenstein, and Wolfenstein: Enemy Territory, both developed using GtkRadiant. It's also home to the official support forum for Q3Map2.
- Urban Terror Forums
- Urban Terror is a free multiplayer tactical shooter built off of the ioquake3 project. They have a community of level designers interested in making maps for the game.
- MapCore is a general level design community of various engines, including id Tech.
Sometimes the best way to get help is to have a live dialog with other people. IRC is a protocol for real-time group communication. If you are going to be using IRC often, you may need an IRC client. Otherwise, web based options exist on most popular servers.
- irc.quakenet.org #radiant
- This is the official GtkRadiant channel. You can chat about level design, texture creation, modeling, programming, development and bugs.
- OpenArena's Resources & Tutorials
- A link list of a variety of mapping resources and tutorials on the web.
- Worldspawn Archives
- Worldspawn hosts a great set of tutorials for beginners.
- Quake Wiki
- Quake Wiki is a blog/wiki/resource site, including backups of the old user sites that were once hosted by PlanetQuake.
GtkRadiant depends on community testing, so filing bug reports is encouraged. However, there are a few guidelines to follow when reporting bugs to make sure that your report is both relevant and reproducible. If in doubt, you can try reading some of the existing bug reports as examples, or you may want to try getting help from more experienced contributors via forum or IRC.
- Make sure you are using the latest version of GtkRadiant. Try downloading the latest in-development builds to see if the problem has already been fixed.
- Search the issue tracker to see if the bug has already been reported or fixed.
- Open a new issue report form and fill out the bug report with as much detail as you can.
- Make sure the title summarizes the problem.
- Accurately describe how to reproduce the bug in precise steps. If it cannot be reproduced, it will be difficult to fix.
- Precisely describe the observed result and the expected result.
- Check your settings and configuration in case these are relevant to the problem.
- Make sure you list your relevant hardware, operating system, version of GtkRadiant, or any other system information.
A note about feature requests: the development team will probably be very busy fixing outstanding issues, and improving the code base for stability. Feature requests are currently best posted on a forum to see if there is enough interest before being filed.