Attention! This is a legacy build of the Mega Man RPG from 2017 and is no longer being maintained.
Reported bugs will not be fixed and any progress made here will not be saved.
Return to the archive index for more legacy content or
play the current version of the game for all the new stuff.
Basically, you have to refresh change tab in order to be able to change another player field for the same doctor. Changes only take effect only after you've refreshed the page changed tab as well.
(Also could you add formatting help somewhere... I forgot how to add images, and had to check my old posts)
Well uhh... the game got stuck again in a player battle against Adrian, the game didn't send me a message about reconnecting. So I decided to give the old "Reload frame" trick a go, and this happened. It probably isn't a bug in itself but I thought that sharing wouldn't probably hurt anyway.
Player Fields being laggy + other stuff Posted by Brorman on January 14th, 2014 at 8:21am Viewed 963 Times
Posted on January 14th, 2014 at 9:35pmEdited on 2014/01/15 at 1:25pm
Posted 2014/01/14 at 9:35pmEdited 2014/01/15 at 1:25pm
#1
Oh boy. Looks like more memory issues. On the one hand, this is absolutely horrible and I'm crying inside every day that the problem persists. Both on the other hand it's forcing me to re-evaluate a lot of my code and make the optimizations necessary for the next 10, 20, 30, 100 robots added to the game. I will keep this open until I can fix everything, and thanks again for reporting. It at first your refresh doesn't succeed, just wait a moment and try again I guess. :|
I have massive lag on all of Doctor Lights' chapter five missions, I can't even get past the third because I have to reload my game. Maybe it'll be better tomorrow...
Lag is a hard thing to pin down the source of and is such a general thing it's hard to dedicate a single thread to it. I believe some of this was being caused by the old server's memory limit, and then later the new server's memory (before I implemented a swap disk), and now I think it's just being caused by high-traffic. I have a bunch more ideas for optimizing the way the game handles data, but they're not something I can finish overnight and will take several months. With that being said - and the Danger Bomb issue having it's own dedicated thread elsewhere - I'm locking this thread until further notice. Thanks for the report though! :)
6 Comments