Bug Thread

[monkeycrew]

I saw that Bat Masterson on the official forums is looking for a list of all the bugs, so I'll list some I have seen. Be sure to add yours.

* The texture stretching on the Presidio counterparts is on at least Caracticus. It is so annoying.
* No attacks or teleporting, basically, for some of the PvP pets.
* The Machine beginning cutscene skips, glitches, and can be skipped by going to the room just as it's playing w a team, no matter the amount of players.
* Can't join the Obsidian Scratch battle if I teleport to someone. At all.
* The Yuletide companions have no promotions or very many epics to choose from.
* I'm prone to losing connection in the Tower of Moo Manchu often. And it is just the tower; most of the time it is in that instance I lose and regain it.
* That Mormo promotion glitch.
* The navigator points to "Stormgate to MooShu" instead of "Hamamitsu Skyway".
* Andalusian Skyway has no navigator point.
* The stormgate to valencia (and I think Marleybone) have no navigator points in Hamamitsu Skyway.
* Players still are prone to turn invisible in the Tower!!
* Iirc, armada enemies in the Dreadnaught (dreadnought*) just teleport and attack with no animations.
* In Fast combat, come critical tunes and sounds (LIKE THE MOOSHU 5'S) are not in-sync with the attack.
* Any new stormgates after Valencia 2 in the worlds from Florenza Skyway (which should be spelled Florenzia) have no navigator point in their respective skyways.
* Florenza's unfortunately misspelled. In past quests, it's spelled Florenzia.
* Many, many mismatched dialogue to text errors.
* Using a Haywire Strike on the Ebon Head triggers the old Hydra bug, in which you have to flee and start again.
* In the Machine, the cutscene will play before all the chests have been collected, causing the loot to be lost.
* Rewards from the Party Barge Ambassadors give no Privateer items. Witch and Musket rewards are max level ones only (correct me if I'm wrong - I saw Willow's post on the forum)

Be sure to add some, and maybe KI will see them.

EDIT: If anyone wants to refer this on the message boards, my name on there is CaptainBlackWolfBowman.

ALSO EDIT: I will add bugs noted here to my list above.

[ToonTown565]

I'm prone to losing connection in the Tower of Moo Manchu often. And it is just the tower; most of the time it is in that instance I lose and regain it.

does this happen to you on a regular basis? my connection is fine in tower, could just be your connection coincidentally getting awful whenever you decide to do tower runs, but still something worth looking into.

bugs wise, idk if this is a bug, but using a haywire strike on the ebon head in hydra can cause the bug to come back (it's different though. the example i have is, the ebon head was at roughly 2k, (so at half) and i did a hidden haywire strike, and crit, doing around 3k. which caused it to die, but then it thought it was time for it to go back down into its 3rd phase, so it bugged out, not allowing me to finish the fight, i had to flee, and go to mitch to revive my 3 comps, and reset the fight to continue.) if devs could look into that it'd be cool

[Stephanie]

I've posted about this before, but some people will experience a glitch with the Aquila main quest "Bring Me My Bow," where they get stuck in an endless time loop and can't continue. (You can find old threads about it here and here.) I personally experienced this glitch on my swashbuckler, and Customer Support had to manually add the next quest into my quest-book for me. It would be great if KI looked into actually fixing this issue because it's rather serious, and not everyone knows to contact support.

There is also a pretty comprehensive list of PVP bugs that @Nojow posted on the official forums (thread here). Bat said he passed it on to the team, but it's been more than a month and the bugs remain unfixed.

Another bug (thread here) is that after resetting a companion's talents and giving it health, that companion's health will be glitched on the first battle, so people are currently having to flee and restart the battle when that happens.

[monkeycrew]

does this happen to you on a regular basis? my connection is fine in tower, could just be your connection coincidentally getting awful whenever you decide to do tower runs, but still something worth looking into.

bugs wise, idk if this is a bug, but using a haywire strike on the ebon head in hydra can cause the bug to come back (it's different though. the example i have is, the ebon head was at roughly 2k, (so at half) and i did a hidden haywire strike, and crit, doing around 3k. which caused it to die, but then it thought it was time for it to go back down into its 3rd phase, so it bugged out, not allowing me to finish the fight, i had to flee, and go to mitch to revive my 3 comps, and reset the fight to continue.) if devs could look into that it'd be cool

Not too often it does happen, but it's more than rarely.

[Crushcut]

I'm just gonna drop my Machine dungeon bugs thread here as another source of reference:

http://www.pirate101central.com/foru...NOW-Kingsisle!

[Kingurz]

Unfortunately, the issue isn't KI awareness of the bugs. These bugs have already been posted to the official and Central forums multiple times. Granted the community manager is one of the newest members of the team and may not be personally aware of some of these, but several of these bugs WERE identified while the current community manager was in the seat....but haven't been fixed in an update since.


The issue remains the fact that Pirate101 doesn't get many updates at all. The most telling aspect of that thread is the following statement from the community manager, "We have our own tracking lists internally of course, but we want to make sure we're in line with the community's own reporting here. Prioritizing the most globally wide-spread issues at the top, of course". It almost sounds like KI is admitting they will not fix all the bugs, but rather only fix the "top voted" bugs by the community....when they get around to actually working on Pirate101.

Remember, that whole thread on the official forums started because a player asked them to work on known bugs since it didn't appear that new content or a test realm would be available for Pirate101 this spring (unlike Wizard101).

I was hoping KI would have responded to that player in something like, "yup, we're tracking most of these bugs and are working on them now, but please post any we may have missed," instead of, "we will work on our internal bug list as soon as the community tells us which ones are more important".

[Willowdreamer]

Unfortunately, the issue isn't KI awareness of the bugs. These bugs have already been posted to the official and Central forums multiple times. Granted the community manager is one of the newest members of the team and may not be personally aware of some of these, but several of these bugs WERE identified while the current community manager was in the seat....but haven't been fixed in an update since.


The issue remains the fact that Pirate101 doesn't get many updates at all. The most telling aspect of that thread is the following statement from the community manager, "We have our own tracking lists internally of course, but we want to make sure we're in line with the community's own reporting here. Prioritizing the most globally wide-spread issues at the top, of course". It almost sounds like KI is admitting they will not fix all the bugs, but rather only fix the "top voted" bugs by the community....when they get around to actually working on Pirate101.

Remember, that whole thread on the official forums started because a player asked them to work on known bugs since it didn't appear that new content or a test realm would be available for Pirate101 this spring (unlike Wizard101).

I was hoping KI would have responded to that player in something like, "yup, we're tracking most of these bugs and are working on them now, but please post any we may have missed," instead of, "we will work on our internal bug list as soon as the community tells us which ones are more important".

Yeah, my post expressing disappointment that there wasn't already a list being worked on based on what had already been reported didn't make it through moderation on the main boards. Your thoughts were the same as mine. I can't fault @Bat Masterson for his attempting to engage the community now and then, but honestly -- there have been many, many compilation threads posted by now, and we all have different priorities for fixes depending on how and where we play.