The only supported Ares versions for end-users are the publicly released stable versions.
- Any version that is not one of the publicly released stable versions is a testing version and only meant for testers.
- Anyone who is using a testing version despite not being a tester is not entitled to any support from us. If you're not a tester, you weren't supposed to use the testing version in the first place.
- Testing versions are not released or marked as stable versions because they're not fucking stable. Any particular testing version could unexpectedly and randomly be utterly broken and unplayable. They can be unstable, subtly flawed, features can randomly be broken, they can be slow due to excessive debugging code, or can be built for a very specific purpose only the testers know about. Using testing versions without being a tester is an invitation of trouble and frustration and nothing else.
- Testing versions can be outdated rapidly. In a development cycle, it's entirely possible there are multiple new versions per hour, each one fixing issues that existed in the one before, or introducing new issues. Picking one at random is akin to Russian roulette. Just because a build is the latest version released doesn't mean it's the most stable build of the past 24 hours. Educate yourself before picking an unstable version.
I will repeat this once more, since certain elements in this community are famous for their dimwittedness and nothing else:
Any version that is not a stable version of Ares is inherently unstable.
If you use a testing version of Ares and complain about any of its properties, specifically in regards to bug counts, stability or feature completeness, you're a fucking moron. Period.
We do not support end users using the testing versions of Ares. We didn't lock them away so far because there wasn't much of a reason to, but if it comes to a point were wide-spread use of testing versions creates problems of any kind for us, we have absolutely no issue with preventing testing versions to work for anyone but testers.
As we have discussed just recently, the community had chance enough to join the testing crew and get the testing versions in advance, it had no interest in that, so it shouldn't turn around now and try to obtain the testing builds.
If you figure out where the testing builds are, good for you.
If you know how to get them, shut the fuck up. They're not for public consumption.
On the related topic of distributing mods with Ares, the following can be said:
- In any situation, adhere to the license. To put this simply, your right to redistribute Ares is founded on your acceptance and adherence to the license it is under - if you violate the license, you don't have the right to distribute Ares, legal or otherwise. Before you redistribute Ares with anything, read the goddamn license and act accordingly. It's right there in every release, so don't pretend you didn't know.
- If you're distributing a stable version:
- Always make sure your Ares is up to date. We only support the latest public release, and if anyone with an outdated version asks for support, our first and only suggestion will be to update to the latest stable release. Patches exist for a reason, we don't release them for fun. If you're distributing your mod with an outdated version and/or your mod is incompatible with the latest version, you're risking support troubles and you're risking broken games.
- If you or your users uncover Ares issues, report them to the bugtracker.
- Make sure you deliver Ares cleanly. Do not distribute a virus-infected Ares.
(Sidenote: Since a virus modifies the Ares binary, and you would not mark Ares as modified in accordance to the license, you would technically commit software piracy by distributing a virus-infected version of Ares. Just sayin'.)
- Always make sure your Ares is up to date. We only support the latest public release, and if anyone with an outdated version asks for support, our first and only suggestion will be to update to the latest stable release. Patches exist for a reason, we don't release them for fun. If you're distributing your mod with an outdated version and/or your mod is incompatible with the latest version, you're risking support troubles and you're risking broken games.
- If you're distributing an unstable version:
- First of all, you're stupid. Plain and simple. Releasing your mod based on and with software that has officially not been deemed stable is in no way smart.
- If you're doing it anyway, we expect the following disclaimer in very clear view in an unmissable place:
Ares Testing Version Disclaimer WroteThe version of Ares distributed with this mod is an unstable testing version not meant for public consumption. The Ares developers do not support the usage or distribution of testing versions with public mods. This version of Ares has a certain likelihood of being broken in various ways, including, but not limited to:
* frequent Internal Errors
* broken features
* incomplete features
* frequent Reconnection Errors in multiplayer
* broken stock functionality
* degraded performance due to debugging code
We, the authors of this mod, consider this version of Ares stable enough for general distribution, but we are required to stress that the Ares developers disagree and do not support this move.
- Do not dare blaming us for your mistakes. Should it turn out that you distributed the wrong version and your mod's players are angry, don't you fucking dare blaming Ares - it was your stupid decision to include a broken testing version with your mod. We told you it was a stupid decision in the first place. It's your stupid mistake, and it's on you to take the blame.
- Do not advertise the inclusion of Ares any more than required by the license. Do not go forward and boast about all the awesome additions made possible by new and not-yet-publicly-released Ares features. If you want to include a testing build, do it quietly. (Except for the loud disclaimer, obviously.)
- Choose. fucking. wisely. As said above: Just because something is the latest build available doesn't mean it's the most stable build available. The latest version could introduce horrible bugs or even intentionally be only half-finished. If you must include a testing version, make an educated choice which build to include, and make note of known issues with that version.
- First of all, you're stupid. Plain and simple. Releasing your mod based on and with software that has officially not been deemed stable is in no way smart.
tl;dr: Don't use testing versions unless you're a tester. If you know how to get the testing versions, stfu about it. If you distribute testing versions with your mod, accept the consequences.
This post is a living document and may be modified and amended at a later point in time.
