[stonyarc]

Originally Posted by TygerTyger

I think quite simply a subsection for public betas will be your best bet. There's no fair way - or at least, fair and managable way - to determine who should and shouldn't have access to a beta. A beta subsection with a bigass THIS IS A BETA and THIS IS WHAT A BETA MEANS faq-style quick explanation at the header of every hack thread, with the mod explanation/instructions etc below it, will serve you best I reckon.

The fact of the matter is that the problem isn't the mods, or the authors, or the forum. It's the people who don't bother reading, are too inexperienced or short-tempered or lazy or all of the above. Make it clear, give them fair warning and if they still don't make an effort, they earn what they get. Sounds harsh, but that's just the nature of forums. The benefits will be there for those who want them as well.

Tyger is right.
Just on the googlemap I got some great responses and some nice feature suggestions from people that have bothered to read what's it about, how it works and what are the known issues (that's why it's a beta).

But some people don't read. If if it says "to fix issues xxxx download latest version". It sometimes frustrating but it's for them and for ourselves we make it. The least they could do is use the page search.

The faq seems like a good idea. Why not make a basic documentation package mandatory with just the core elements in it:

- how to install
- how to configure
- how to uninstall
- known issues
- roadmap
- version history
- tips & tricks

That should avoid the repeating questions and make it a standard additional feature for all modifications.