Mega Man RPG Prototype Bug Reports

With a huge program like the Prototype, there's bound to be some weird bugs and oddities every now and then. Instead of making a thread for every bug, I am collecting them all in a single thread. This thread briefly mentions all kinds of unusual experiences I've encountered, and any way I can think of to reproduce it. Some oddities are so unusual that it came down to luck, and may not even be encountered again...maybe. This thread will get updated every once in a while. My most recent bugs are reported first, and any bugs that I had reported previously are removed if I feel they no longer affect the Prototype. That's all for the notes, enjoy a thread full of bugs in it.


Special Bug Notes

6/3: One Mystery Solved Behind the Robot Clones

I would have reported this earlier, but I needed someone to confirm my "fix" works. So a few people on here reported, after either the server being slow to respond or their connection suddenly being unstable, that they end up with an extra copy of one of their robots on their file, and both robots get glitched up (aka they stay at the same level no matter how much you train them), basically making them unusable. It is still unknown how exactly this bug occurs, but there is an easy fix for it (though it was too late for one particular person...). Follow these steps to resolve the bug:

1. Move the duplicate robot onto the same Doctor that has the "real" robot (I would just make sure it is the same Doctor that unlocked the original robot). You'll know which one is the duplicate if the robot just has the Buster Shot ability on the list.
2. Exit the robot menu (to another menu), then return.
3. Might be optional, but move the (should be) lone robot to another Doctor, then back.

This should remove the duplicate and allow your robot to work again. If necessary do some grinding to get your restored robot back to what it was before, but otherwise your robot should be just like the other robots now.


Bonus Battles, Bonus Bugs

This is just a collection of some of the strangest encounters I had doing the Bonus Field battles. I do not know how any of these occur, but I only have encountered these one time at the most, so it could just have been a hiccup in the code.





New Bugs


10/16/2016: Field Booster Broken

The item works fine in story battles, but it does not work properly in Player Battles or in the Bonus Battles. The item goes through the effect like usual, but when an attack takes place or the user switches robots, the modifier is set back to the original and thus no boost in attacks occurs.




5/5/2016: Core Mishaps

Two notes I should make regarding the use of Cores to disable robots. The first one is that if a Core is used to finish off the last robot, it still counts as the current turn, so for a one turn run of a match, it is possible to use an item, attack, then use another item and still have it count as one turn. Might not have been intentional, though I will admit this bug does more help than harm for the player. The other note is why I'm reporting this bug, though. If the above scenario happens, there is no disable routine for the disabled robot, instead the battle log goes straight to the end of the match routine, meaning no possible item drops for any robot disabled in this fashion, and I would even bet no stat points or experience for the disable either. What is untested is if this can also occur when this is NOT the last disable of the battle. I shall edit this report when I find out more.

EDIT: Ok, this is a really weird bug. I think the pictures will speak for themselves, but a benched robot will NOT switch to the active position until the player actually makes a move after a robot is disabled by a thrown Core. Oddly, though, the disabled robot will finally do its disable routine, and the turns afterwards are back to normal.




Possible Still Existing Bugs (this'll remind me to test to see if these bugs still exist)

6/3: No Stat Points after Crash Bomber disable

If a Crash Bomber goes off on its own and disables a robot at the end of the turn, the one who fired the Crash Bomber does not get credit for the disable, and thus, Crash Man did not get the stats from the disabled robot. On a side note, Magnet Missile triggers the bomb early for some strange reason. It happens every time.




5/25: No WE Regen with Crash Bomber:

While training Crash Man's Defense, I decided I would let the Crash Bombers go off to destroy the bench as I kept launching the bombs. However, something wasn't adding up: My WE would not regenerate on some turns. As it turns out, no WE is regained on a turn the Crash Bomber goes off and disables an enemy robot. I suspect it has to do with how the ability is coded...as you have to use up 1 WE just to activate a bomb early too. The road back to a fully powered-up army continues to hit a few bumpy spots...





5/14: Disabled Robot, Stay Disabled!:

Wow, Adrian, this is yet ANOTHER thing your changes to Rain Flush broke. I just now had a robot target a robot that was alive prior to Rain Flush being used, but before the enemy robot was able to make a move, the target robot was disabled by friendly fire Rain Flush...yet the AI goes with it anyway and attacks the disabled robot...thus the target robot getting disabled again. Maybe the change to Rain Flush needs to be reconsidered...? Btw, this was against Phantom Man in Player Battles.




4/15: Friendly Fire on the Enemy Team:

No screenshots for this one, but this is easy to reproduce. When a robot gets disabled by an ally's attack on the opposite side (aka Rain Flush), the game goes through the messages of your robot downloading data, and even dropping items, but you do not actually get these benefits. This one I PMed Adrian about since I figure this is an easy bug to fix. This is all a graphical bug.


4/12-13ish: Toad Man Versus Rain Flush:

This happened during a fight against n30n. Nothing out of the usual happened prior to this. I decided to use Rain Flush while n30n's Toad Man was the active robot, trying to take out Dive Man on the bench. Instead, the stuff in the screenshots happened... (to sum it up, the enemy Toad Man somehow took damage but not Dive Man, but the game acted like my Toad Man was actually taken out, and I was forced to switch to Bubble Man even though my Toad Man survived. When Bubble Man got disabled, I was able to switch back to my Toad Man).




3/23: Field Support negating Starforce?:

Well, this is certainly unexpected. So for those curious, this is against Copycat in Player Battles that I encountered this glitch. Roll's Field Support removes all benefits and restrictions from the elements in the field, much like the other support robots and also the copy bots. However, this was unusual: my attacks on her dealt damage like they were not influenced by Starforce. The other robots took damage normally. Her case is special because I've dealt damage to other robots who used Field Support on the same turn and nothing out of the usual happens. I used a single target move just in case it only happened with aoe attacks like Rain Flush (and I repeated trying to get Roll with Rain Flush on the same turn she used Field Support, same effect). Bizarre...but I can see why this glitch was easily missed...very special conditions this was found in! So yeah, have some pictures of this strange glitch.

Update (5/15): When Rain Flush is used, the robots on the attacker's side of the field take normal Starforce-boosted damage, but not the enemy team. This makes the support robots very annoying to fight when you need to finish a battle quickly.





10/7: Mecha Support Buginess:

Well, to keep this short, Mecha Support in Player Battles sometimes causes a glitch where your attacks actually end up being redirected to hurt your team instead of the other team. This last report in 2014 was against ThatGuyNamedMikey in Player Battles.