BombermanBoard

Someone64 · #172 Posted: Wed May 28, 2014 1:46 am

My head almost exploded into little bits and pieces upon checking this OP of this thread.

Some feedback: The bombercarts tilt left and right even when moving up and down which looks quite strange. Also, can you make it so that bombs are forced to be released when they reach max charge distance?
Will update post when I find more things. Great work btw! :D

Also, question. Will something happen if I put a rapid fire script to one of my buttons and hold it for about 6 seconds in the title screen?

Good thing there's a force draw option in that cute ass pause menu because this:

Spoiler:

The level generation should include having at least one empty space beside the warp points. Also, for some reason the AIs really didn't want to throw bombs at us and for some reason there are some warp points that don't work no matter how much you step on them. Lastly, MILK!? That's something I REALLY didn't expect you to add.

Is it normal for the game to freeze a little when I start a round? Sometimes it doesn't and it freezes for even longer when I start a wide stage round.

Spoiler:

Major screenshot fail. I was too late. :/ The problem was that I was able to jump into his foot while he put it down but when I took the screenshot he raised it.

Bug report:

Spoiler:

Code:

___________________________________________
ERROR in
action number 4
of Begin Step Event
for object bomber_obj:

Error in code at line 9:
if ( s.z == 0 && s.zspeed == 0 && s.remote && s.alarm[0] > 60 )
^
at position 13: Unknown variable z

Happens when you use bead bomb and immediately put your shield up afterwards.

Probably my 10th edit or something. Is it a bug that using Green's dash move causes me to be invincible for the period that I dash in? I'm asking because it happens in some rounds but in others it doesn't. But if it does happen in that cetain round, it will happen consistently throughout the round.

Pressing back from one of the match settings screens causes the game to swtich from maximized to small window. For some reason I was able to consistently reproduce this bug right until I started typing about it to check which settings screen exactly since it always happens to the same one. After many tries I can't seem to do it anymore.