For example, v2.0 means that everything in that errata doc has been corrected in the second printing, v3.0 means it's all been corrected in the third printing, etc. X: Identifies the printing the errata is for. 231, "all applicable launchers on the unit must be enhanced in the same fashion" - so the SRM 4 must have Artemis IV to match the LRM launcher. The mech carries a LRM 15 with Artemis IV and a SRM 4 without Artemis. Lastly, do not use emoticons in your reports.
Instead, make one post, and edit any subsequent discoveries into that. Don't make multiple short posts in a row in a short time period (e.g. If reporting errata resulting from a post by a writer or developer, include a link to that post.
#Xenoshyft rules errata software
* THE CORRECTION: If a BV correction, please enclose or attach your entire BV calculation and how you made it (by hand, SSW, MML, Heavy Metal etc include version number of any software used). * THE ERROR: Information on the error, preferably using direct quotes when applicable, and why you think it's an error (if not obvious). * LOCATION: Relevant page number(s) and section titles. If the product has multiple printings, note which one you're referring to. * VERSION: The first post in each thread will always list a product's version history, if any if there is no such note, skip this step. As new errata always overrides the old, such corrections take precedence over any previously compiled errata document or webpage.Īll errata reports should contain the following info: If so, errata listed there is considered official. The first post of each errata thread may have a section labelled " Developer-Level Errata". The official, compiled Errata can be found here: If posts follow a consistent template I can work much faster, and am far less likely to miss your report. If you want to discuss a piece of errata, or any other part of the errata process, please use the stickied Errata Discussion Thread.Īll errata reports should be laid out in the same manner, following the template described in the next post. This will speed up errata compiling and help ensure your report is not lost in general chatter. If you're not making a report, don't post in an errata thread (only writers, developers, and MUL Team members may ignore this rule). Posts that fail to follow these rules will be edited or deleted. In addition to the normal forum rules, there are a couple of additional rules that all errata reports should follow. if there's a problem that doesn't belong in Rules Questions or Ask The Writers (such as typos, record sheet errors, etc.) just go ahead and post it as errata. Once you have your answer, THEN make an errata report.
If a non-rules question, it likely belongs in Ask The Writers. if there's a rules problem but you don't know the answer, ask in the appropriate Rules Questions subforum.
In general, if there's a problem AND you know the answer, make an errata report.