|
|
Post by Firemaster on Aug 14, 2008 15:15:36 GMT -6
 I know it wasn't a really good screenshot because you cant really see details. But I'll describe it for you. In the tent is Firemaster and Firemaster2. In the battle(ambush) is,,, Firemaster and Firemaster2... I disconnected in battle and when I came back I found that. Any more detailed explanation? |
|
|
|
Post by U. Dye on Aug 14, 2008 19:53:48 GMT -6
Yeah, I think Soren said something about this being an old bug Kija hasn't been able to kill. Probably nothing to worry about.
|
|
|
|
Post by Jumin on Aug 14, 2008 22:16:10 GMT -6
so.... is the battle actually still going on in that ambush? or are those just empty icons?
|
|
wizkid17
Explorer
Ben The Great the Paladin Knight
Posts: 61
|
Post by wizkid17 on Aug 15, 2008 7:35:05 GMT -6
wow, never saw that before
|
|
|
|
Post by Firemaster on Aug 15, 2008 8:22:24 GMT -6
so.... is the battle actually still going on in that ambush? or are those just empty icons? Probably not.. When I disconnected I logged out with only 1 more monster.. And that was a Lower Demon that I stopped. Poor guy was in there all alone and paralyzed. Lawl. I would've assisted myself but it was an ambush. And then I also realized I dont accept assists =O. |
|
|
|
Post by Kija on Aug 15, 2008 12:52:52 GMT -6
There is a slight bug that can cause battlemarkers, not the actual battles as far as I know, to still remain on the map if a player disconnects at the right moment. I have done some to prevent it, but I have really wanted to focus on getting the newer battle engine out instead, rather than do a bunch of fixes that are not even going to matter when the new one is finished. So, for the most part, unless the battle bug is pretty bad, such as one that can change the outcome of a battle, I usually do not go too far into it.
|
|
|
|
Post by Firemaster on Aug 17, 2008 13:47:36 GMT -6
There is a slight bug that can cause battlemarkers, not the actual battles as far as I know, to still remain on the map if a player disconnects at the right moment. I have done some to prevent it, but I have really wanted to focus on getting the newer battle engine out instead, rather than do a bunch of fixes that are not even going to matter when the new one is finished. So, for the most part, unless the battle bug is pretty bad, such as one that can change the outcome of a battle, I usually do not go too far into it. Yeah it wuold'nt really make much sense trying to fix something un-important when your almost halfway done with something more important. The bug doesn't affect anyone, so whats the ppoint of it being fixed when a new Battle Engine is halfway done? Vroooom Vrooooooooooooooooooooooooooooooom!!!! |
|
