Format

This is a casual format. Chat, discuss and add bugs as you please. No need to create subpages. Just add to the 'bug discussion and feedback' section for whichever version you're playing. I will generally categorize things and remove old discussion related to bugs that have completely fixed. Note that to keep this page current, discussion on this page will generally not be archived once the related bugs have been fixed.

To do before next release

To be determined

Fixed in Development Version

None yet

Known bugs

Undecided concepts

To do before V1.0.0

Getting out of 'stuck'

A bug is a bug. But, two types of bugs in particular should never end the game. Display corruptions and characters who get stranded, either in the dark or encased in impassable terrain.

Display corruptions: are a result of me miscounting save and loads that occurs about every ten lines of dialogue. If your display becomes corrupted, save, exit and re-load the game. The display should fix itself.

Character is trapped in a dark map, or encased in impassable terrain: This is prone to happen in unfinished areas, like Ravens Garage. Certain sequences of active character swapping can sometimes result in a character encased in the wall in the extreme northwest corner of Tokyo. To get out of situations like this, use your cell phone to swap to a different character in a different location. Then call the stuck character and ask them to return to base.

V050 bug discussion and feedback

BucketMan: I am so looking forward to feedback on this. :)

EtMarc : Well, the crash is not the T-Engine fault, but yours *grin*. Even after unpacking the team file it doesn't work on Linux, because the script/ai/init.lua file use the UPPERCASE version of some AI files. Since you are on Windows, it still worked for you, but the T-Engine is case-sensitive, so it didn't find the scripts.

NerdanelVampire: Here are some new bugs:

NerdanelVampire: The newest bug: the subway entrance near Hot Leg leads into stuck inside a wall.

NerdanelVampire: The funny thing is, I have already discovered four bugs but I have yet to see combat of any kind. The only reason I've been starting new games is that there's no point in not restarting from scratch since I've done nothing but trying to get my bearings in the game.

BucketMan: Two things:

NerdanelVampire: I read the guide. I just haven't actually started playing since I want to get a little more familiar with everything so that I don't get banned from money-generation travel missions for each of my characters or something permanent like that. (Yes it has been out a couple of days, but I have been otherwise occupied a lot.) Bubblegum Crisis has a formidable learning curve. It's also not nice to run into a timed event that I'm too weak to handle because I haven't gained power at the expected rate while wasting my time getting accustomed to the map.

BucketMan: The game does have a steep learning curve, yes. :) I'll try to get those bugs fixed, and maybe implement apartment buildings this weekend. Thanks for the bug reports. Let me know if you come up with anything else I may be able to squeeze in in the next few days.

EtMarc: I got this error message after killing a mission target :

error: attempt to index a nil value
stack traceback:
   1:  function `choose_ks_to_attack' at line 924 [file `/scripts/combat.lua']
   2:  function <12:file `/scripts/ai/mission_ai.lua'> at line 17

EtMarc: Also, is it a bug, or if you take an ally with you, they are supposed to move half as slowly as you do?

Sirrocco: a couple of things.

V055 bug discussion and feedback

BucketMan: Ok. I've cleaned up most of the things people complained about.

Sirrocco: and I've found a bunch more. Some were already mentioned in Gameplay (Mackie doesn't work, endo torso can't be targeted even after exo is destroyed, apartments essentially impossible to enter) and others follow.

EtMarc: When I use the 'l' look command, sometimes I get a description of the person, instead of their name (it happened for a beginner assassination mission with a bunch of bodyguards, are they supposed to do no damage at all?). This comes with that error message:

error: attempt to call a nil value
stack traceback:
   1:  method `describe' at line 264 [file `/engine/target.lua']
   2:  method `target' at line 491 [file `/engine/target.lua']
   3:  function <713:file `/engine/target.lua'> at line 730

Also, I found out that asking for the map tutorial at Tokyo Express blanked my screen until I reloaded the game.

Lastly, I went into Area 2 apartments, where a boomer was (Leon and co where outside). I was Sylla with Priss and Linna, but I couldn't see the boomer, and Priss and Linna got damaged by the boomer even before the door got opened. I wonder if it is due to the party combat, or it is a more severe bug. Here is errors trace:

error: attempt to call a nil value
stack traceback:
   1:  method `describe' at line 264 [file `/engine/target.lua']
   2:  method `target' at line 491 [file `/engine/target.lua']
   3:  function `get_aim_dir' at line 706 [file `/engine/target.lua']
   4:  method `ranged_fire' at line 6504 [file `/scripts/hardsuit.lua']
   5:  function <3407:file `/scripts/bgc.lua'> at line 3460
error: table index is nil
stack traceback:
   1:  function `boomer_dead' at line 486 [file `/scripts/combat.lua']
   2:  function `boomer_actually_melee' at line 295 [file `/scripts/monster.lua']
   3:  function `boomer_combat' at line 148 [file `/scripts/monster.lua']
   4:  function <12:file `/scripts/ai/boomer_a.lua'> at line 25

Sirrocco: forgot one from earlier - random tourists picking up boomer corpses. Must be something in the water, no?

Modules/Bubblegum Crisis/Bug discussion (last edited 2008-10-09 13:31:49 by c-68-49-208-225)