ArmA: Armed Assault: Bug List

⚠

Bug additions are to be clear and concise. Information on how to reproduce and locate bugs or visually displayed with a movie or image is essential in helping BI fix any bugs as quickly as possible. Your additions are to be signed and version number properly identified or your addition will be removed without notification.

Introduction

Help BI keep track of important bugs by contributing to this list! Before you begin editing, read over the How To Report section. Its very important to provide accurate detail by posting reproducing steps, images, movies, and locations of bugged models/graphics.

If you have a more detailed bug report that requires more room then makes sense for the Biki then go to the BIS Forum and find the current bug thread and post it there.

There is a Wishlist for making suggestions to improve Armed Assault, please use this list for those suggestions.

If you are unsure whether something actually is a bug, or perhaps just misleading documentation, or whether it is supposed to behave in this particular way, post your report in the Bug or Feature? list.

You should only post bugs about the current version

Current ArmA version is: [1.02]

Current Dedicated server version is: [1.02]

You can find information about the 1.02 patch here

The old bug list can be found here Armed_Assault:_Bugs_List-version-1.01.5094.

How to Report

Submitting bugs in a usable format is essential. Your wasting everybody's time if you post something meaningless and there is a good chance your addition will be removed or ignored.

1. Post in the appropriate section.
2. Always sign your entries by adding ~~~ after your addition. Failure to sign your addition will result in someone removing your addition without notification.
3. Add your bug using the template Bug priority with priority 0 add the end of the appropriate section. Authorized people will alter the priority of your bug.

The source code of a new bug with the template Bug priority should look like that:

{{Bug priority|0|
YOUR TEXT HERE -~~~
}}

Here are a couple of decent examples of usable information.

Reproduction missions can be very helpful for complex problems, when possible provide a link to the mission containing only the necessary items to illustrate the bug report.

How to mark bug fixed

To mark your bug fixed, edit the page and replace the priority number with an x. This will strike out the bug as fixed.

 {{Bug priority|x|
 90% of the time when getting out of a boat the player is placed under the ground. ''[1.01.5094]''.[http://img291.imageshack.us/img291/8614/armartn1.jpg check image]}}

⚠

Bug priorities To make it easier for BI people to see important bugs, we introduced bug priority templates. Add new bugs with priority 0. BigDawgKS, Plaintiff1, the BI staff, and the wiki sysops will set priorities to values higher than 0.

Multi Player Issues

{{Bug priority|0| If a player has a squad of AI under their command and that player disconnects. When another person joins their slot (the player who left), the AI will constantly be yelling commands at the new player and will follow them wherever they go. The player will not have any type of control over these AI, and they will not stop for anything.[retail v1.03] --Cam51

A couple of things:

There is no retail version v1.03.

In the meantime, you can try openning the command/communicate dialogue by pressing 0 (which enters the 'reply' menu, I believe), and then hitting 1. This tells the AI that you're finished doing whatever it believes you to be doing.--Plaintiff1 07:22, 31 January 2007 (CET)

I'm sorry, I placed the retail in there because I saw people with demo in their version. I guess you didn't understand what I was saying, what I ment was there are NO ai in the command list, so there is no AI to communicate to. If your small fix still stands, then I will pass the info along. [v1.03] --Cam51

Visual Issues

This being the visual issues section, reporting any bug in this section should contain a screen shot of the reported bug.