Found a Bug, Read this first! Thread - CANARI

When finding an issue in a video game, it can sometimes be hard to recreate the problem on a different machine. The fastest way for us to solve the problem is to know whats causing it. For this reason, it's helpful if you include as much of the following information as you can:

Computer Specifications

• Operating System: Ex. Win 8 Pro 64-bit, OSX 10.9.4
• Processor and Speed: Ex. 3.5 GHz Intel Core i7, 3.4GHz AMD FX-8320
• Memory: Ex. 8GB 1600 MHz DDR3
• Graphics Card: Ex. NVIDIA GeForce GTX 775M 2048MB, AMD Radeon HD 7750 1024MB

Game Settings

• What resolution were you playing at? Ex. 1920 x 1080, 1280 x 720
• What controls were you using? Ex. Keyboard & Mouse, Gamepad
• If a Gamepad, which model of gamepad? Ex. XBox 360 Controller for PC/Mac

What actions were taken up to the point of the bug appearing?
Ex. On my third life, I purchased the sonar from the inventory, but after equipping and un-equipping it, it still appeared on the heads up display in game. However, when I tried to use it, the sonar did not work.

If you performed the same action again, does the bug still appear?
Sometimes bugs appear because of errors that were triggered previously. If you restart the game and perform the same actions and the bug doesn't appear, it is likely that something previously in your game caused the error. This information is still worth reporting, but its helpful to let us know whether or not the bug appeared when you tried the same behavior.

What is the category of the bug?
Quality Assurance (game testing) rank bugs into different categories and conditions based on their impact on gameplay. It's helpful to categorize problems, so our team knows which problems to fix first. Here are the categories PixelBot Games considers for bugs:

• User Interface - refers to a problem in the images and words that describe the game state. For example, if the battery life meter of the flashlight stops working or if the Energy Stored numbers are incorrect or malfunction.
• Art Assets - refers to a visual problem with the 3d models, textures, and materials that make up the game. For example, the ground texture looks skewed or warped.
• Performance - refers to the ability of the game to run smoothly. For example, if the game starts to lag after a specified amount of time or if load times increase the longer you play.
• Controls - refers to button presses and input devices. For example, if a piece of equipment isn't working.
• Gameplay - refers to problems that affect the way the game plays as intended. For example, you find a hole in the floor behind a ramp that causes your robot to get stuck and you are forced to restart.
• Audio - refers to problems with the sound effects and music in the game. For example, the background audio stops working.

Bugs are also classified into conditions:
Low - A bug that is annoying, but doesn't affect gameplay.
Medium - A bug that is inconvenient to the player, but doesn't prevent the game from playing normally.
High - A bug that severely limits the player's ability to play the game as intended.
Fatal - A bug that crashes the game or makes it unplayable.
None of this information is required, but giving us as much as you can is greatly appreciated.