- Mar 17, 2012
- 4,293
- 0
This is the master issues list for Pin•Bot. This thread is maintained to aid FarSight in exterminating gameplay bugs, art issues, and sound problems from Pin•Bot.
This thread is locked to keep it clean and focused on actual issues, as opposed to opinions about such issues. Report art issues in the Art forum, and all other issues in a new thread in this table's forum. I will add newly-reported issues to this thread at regular intervals. In addition, each bug has a link to the thread it was reported in; discussion of bugs should take place there.
Latest Updates:
27 May 2013
Status key:
GAMEPLAY ISSUES:
30-001: Local high score table may reset to factory default values
First reported: 25 May 2013
Description: Upon finishing a game with a high score, the other scores in the local high score list may reset to their factory default values.
Devices: iOS
TPA Version: iOS v1.2.8
Status: Acknowledged as 25 May 2013.
30-002: Earning a special or the replay score award credit instead of extra ball
First reported: 25 May 2013
Description: Earning any special or the replay score does not award an extra ball, but instead awards (useless) credit.
Devices: Android
TPA Version: Android v1.14.0
Status: Unknown
30-003: High scores limited to 9,999,999
First reported: 27 May 2013
Description: The local high score list (the one displayed on the table, not the UI one) is limited to 9,999,999 points, even though the table will correctly score up to 100 million.
Devices: All
TPA Version: All
Status: Working as designed. This is a bug carried over from the real Pin•Bot.
This thread is locked to keep it clean and focused on actual issues, as opposed to opinions about such issues. Report art issues in the Art forum, and all other issues in a new thread in this table's forum. I will add newly-reported issues to this thread at regular intervals. In addition, each bug has a link to the thread it was reported in; discussion of bugs should take place there.
Latest Updates:
27 May 2013
- Added high score gameplay non-issue # 30-003.
- Added extra ball gameplay issue # 30-002.
Status key:
- New - Issues that are newly reported.
- Unknown - Issues from a long time ago that have not been followed up in a while so that no one really knows what happened to them.
- Confirmed / Open - Issues that either I've personally reproduced, that so many people have reported that the existence of the issue is not in doubt, and/or that members have posted a demonstration (like a YouTube clip) of the issue.
- Acknowledged - Issues that have been acknowledged by FarSight, but for which no fix exists yet.
- Fix Pending - Issues that have fixed by FarSight, but the fix is in testing or submission process and is not yet available to players.
- Fixed - Issues that have been resolved by FarSight. Note that not all platforms receive bug fixes at the same time, so an issue that is "Fixed" may still be unresolved on some platforms.
- Could Not Reproduce - Issues that were reported, but the issue has not been successfully reproduced.
- Working as Designed - Issues that are bugs or quirks in the actual table, as well as other issues that result from design or licensing constraints.
GAMEPLAY ISSUES:
30-001: Local high score table may reset to factory default values
First reported: 25 May 2013
Description: Upon finishing a game with a high score, the other scores in the local high score list may reset to their factory default values.
Devices: iOS
TPA Version: iOS v1.2.8
Status: Acknowledged as 25 May 2013.
30-002: Earning a special or the replay score award credit instead of extra ball
First reported: 25 May 2013
Description: Earning any special or the replay score does not award an extra ball, but instead awards (useless) credit.
Devices: Android
TPA Version: Android v1.14.0
Status: Unknown
30-003: High scores limited to 9,999,999
First reported: 27 May 2013
Description: The local high score list (the one displayed on the table, not the UI one) is limited to 9,999,999 points, even though the table will correctly score up to 100 million.
Devices: All
TPA Version: All
Status: Working as designed. This is a bug carried over from the real Pin•Bot.
Last edited:
