Time for OUR list of known issues.

[AyumiAmakusa]

Not sure if this is bug related or lag related, so maybe someone can help confirm/deny what's happening.

I've been playing my cleric again (since the Pre) and have (again) noticed that I can target a party member and hit heal and have it still hit me instead of them.

I have all versions of auto-target turned off. I've checked for the out of range and invalid target messages. (I would expect it to not heal them in those conditions.)

It only happens the first cast right after I target them. Its a heat of battle thing. I see someone getting a beat down and quickly select then heal and the heal lands on me without any of the error messages.

Any one else see this? Bug? Lag? Some other explaination?

Thanks.

I experience this. Even though I target someone else and cast a spell, it will land on me sometimes. Again, number 6 of UI bugs.

[KillEveryone]

A hireling that has been told to remain in place will not come when called (unless you first allow them to move again). WAI?

I've had this happen to me a couple of times when I was doing quests in the Delera's area. Part 2 this happened every time and the hireling still wouldn't tele to me after I told it to move.

Can't rember the other quest name. If you go past where you turn to go uphill to Delera's tomb itself, the quest is back in the back. Parked my hireling at the entrance and wouldn't come when I summoned to the alter.

Number 6 of UI bugs.

This may have been what I've been expierencing with my action boosts and why I can't get it to reliably reproduce. I didn't know this bug changed to this.

[AyumiAmakusa]

Acid Fog and Solid Fog do not slow enemies down anymore. Both of these spells have been broken since the game went F2P, almost a year ago now.

I was under the impression that it was WAI, is it not?

[Cahira]

Items:

--Items with no augment slot and minimum guild level (greater than 1) are still dropping. I've mostly seen this in end rewards, but I have also seen it in chests as well. (Bug reported on 6/30 and 8/1)

Quests:

--Reclaiming Memories
----The Skeletal Giant cannot be ranged. Attempts to shoot him or use a ray spell will get no combat feedback or visual effect. The smaller skeletons in the same area can be ranged, so it shouldn't be the geography of the quest. (But reported on 7/29)

General Gameplay:

--In addition to getting stuck in the middle of ladders, it is possible to get stuck at the base of a ladder and unable to climb it at all.

[Angelus_dead]

2. Our "known issues list" is not intended as a list of every bug we know about. It is a list of bugs we don't need more reports about. We very often don't put things on the list because we WANT you to keep filing bug reports on them if we're looking for more information or a sense of the impact of the bug.

Seriously, that is NOT what a Known Issues list should be for. The real function of a Known Issues list is to warn your customers about flaws in your product. It's meant to serve all your users, not enhance the quality of incoming bug reports.

Entries should be added to Known Issues as soon as you're pretty sure the problem is real. It shouldn't require waiting until the problem is so totally understood that no bug reports are needed. If you also want a list of "Topics That Should Not Be Bug Reported", you can create a separate page for that purpose (and that would be a good idea, because it could include intended behavior that inexperienced users misinterpret as bugs)

[stainer]

Giant fail.

Seriously, that is NOT what a Known Issues list should be for. The real function of a Known Issues list is to warn your customers about flaws in your product. It's meant to serve all your users, not enhance the quality of incoming bug reports.

Entries should be added to Known Issues as soon as you're pretty sure the problem is real. It shouldn't require waiting until the problem is so totally understood that no bug reports are needed. If you also want a list of "Topics That Should Not Be Bug Reported", you can create a separate page for that purpose (and that would be a good idea, because it could include intended behavior that inexperienced users misinterpret as bugs)

Speaking of fail.

Hi Welcome

I am pretty sure you do not get to define what Turbine names things. I understood the explanation that was given.

[AyumiAmakusa]

Giant fail.

Seriously, that is NOT what a Known Issues list should be for. The real function of a Known Issues list is to warn your customers about flaws in your product. It's meant to serve all your users, not enhance the quality of incoming bug reports.

Entries should be added to Known Issues as soon as you're pretty sure the problem is real. It shouldn't require waiting until the problem is so totally understood that no bug reports are needed. If you also want a list of "Topics That Should Not Be Bug Reported", you can create a separate page for that purpose (and that would be a good idea, because it could include intended behavior that inexperienced users misinterpret as bugs)

Now now, keep this thread free of disputes so as to not become Cube Food. To talk about Tolero's statement, please go here http://forums.ddo.com/showthread.php?&postid=3166295

[Carpone]

2. Our "known issues list" is not intended as a list of every bug we know about. It is a list of bugs we don't need more reports about. We very often don't put things on the list because we WANT you to keep filing bug reports on them if we're looking for more information or a sense of the impact of the bug.

It would be helpful if Turbine published a list of 'acknowledged as a problem (not WAI) and we need more info' bugs. As players we have no idea if what we discern is working as intended or an actual bug. If there are issues you need more info on, more often than not players are more than happy to provide you a plethora of details.

[Angelus_dead]

I am pretty sure you do not get to define what Turbine names things. I understood the explanation that was given.

Newsflash: It wasn't me who invented what a Known Issues list is. I'm just describing what that term already means. If Turbine decides to do something else and call it "Known Issues" then that is a disservice to their customers.

PS. I see what you're doing, and imagine others can tell too.

[Sutekx]

Another bug that has been reported as well:

Voice Of The Master trinket is not giving the +5% XP bonus at the end of a quest while equipped. Tried and tested in several quests ranging from Gianthold, Vale, Orchard, and Inspired. Does not show on the experience screen as it did in the past.

Reasons why I am posting it here so others can check it as well and also file more bug reports.

[hydra_ex]

10) NEW - Players will notice that upon logging in, your character will be stripped of all equipment and then re-equipped causing any temporary HP and SP increases to be removed.

That makes a ton of sense.

It also explains why I log in with 9 haste boosts/PS instead of 11; my Verik's isn't being put on until after.

Also
Enhancements: WF Greater Weapon Aptitude is completely broken (probably).

[AyumiAmakusa]

Another bug that has been reported as well:

Voice Of The Master trinket is not giving the +5% XP bonus at the end of a quest while equipped. Tried and tested in several quests ranging from Gianthold, Vale, Orchard, and Inspired. Does not show on the experience screen as it did in the past.

Reasons why I am posting it here so others can check it as well and also file more bug reports.

Is this before or after the hotfix on Monday? It was working fine for me before the hotfix.

[Cyr]

* Monsters have amazing abilities to move around at random when stunned, earth grabbed, dancing, or held as long as they are also blind.

[Freeman]

I was under the impression that it was WAI, is it not?

These spells worked correctly for years, up until the F2P update. I have never seen any release note or Dev post indicating that this was changed on purpose. Also, players are still properly affected when the mobs cast it on us. The main problem is that new players don't know it is broken, and those are the players Turbine caters to now.

[Sutekx]

Is this before or after the hotfix on Monday? It was working fine for me before the hotfix.

This Monday haven't tried, last Monday tried and no dice. Also it's nice to get feedback from the players as well instead of the canned response sent via email. But I am going to check it again right now.

[ArtosKincaid]

Is this before or after the hotfix on Monday? It was working fine for me before the hotfix.

It doesn't show on the experience screen, but you do get additional XP, or at least that's the way it was working according to my calculations last week.

[AyumiAmakusa]

It doesn't show on the experience screen, but you do get additional XP, or at least that's the way it was working according to my calculations last week.

Ya, that's what I thought too. I'll leave it up just in case it's a real bug but one more confirmation that it works post-hotfix and I'll take it down. You'll never know what hotfixes will do.

[eulogy098]

I appreciate the effort! Couple of notes for everyone's sanity:
1. If you're reporting bugs, make sure you've done so in the bug reporting tool (which can be accessed outside the game) also. The forums are not a bug reporting tool, and posting them only to the forums can actually delay a fix.
2. Our "known issues list" is not intended as a list of every bug we know about. It is a list of bugs we don't need more reports about. We very often don't put things on the list because we WANT you to keep filing bug reports on them if we're looking for more information or a sense of the impact of the bug.

This is a rubbish excuse for not fixing bugs that are as old as the abilities have existed (great weapon aptitude, http://forums.ddo.com/showthread.php?t=264963)

I think the reality is that there is simply NO EFFORT at all regarding any bug that doesn't directly effect turbine-point-purchasing. If there was, even a shred of effort, there wouldn't be very basic bugs that last indefinitely with no improvement at all.

[shaolaolint]

Two bugs I've had for past year and have reported. Game crashes upon entering some areas almost 75% of the time. Usually entering Necro, Desert, Gianthold, Valen also sometimes adventure compendium, and such are blank.

[MrWizard]

pressing ctrl-g brings up the LFM table...only to have it go to the upper left hand corner, underneath the menu toolbar, map, and my hit point bar (which I put up there).
I have to select it to bring it to front to be able to read it unhindered.


combat feats, trip and stun, sorta work sometimes...most of the time it is highly delayed. On a moving creature it is 100% better not to select it when using trip or stun. If you do select a moving monster it will usually not get a roll, if you do not select and just hit trip or stun, it will usually affect a mob (about a second later, a swing later, and they will be about 10 feet away...but it works).


Clicking anything on the hotbar is a 50/50 that it will work or even be activated from changing weapons, a combat feat, potion, or anything. If moving that seems to go to a 20/80 chance (20% it will work). I usually have to stop what I am doing completely, then select it...wait to see if it works..then move on if it worked.
To heal in battle all I can do is mash the potion of cure serious and hope it takes. 80% of the time it does not and I die...after hitting it 5 or 6 times, it never gets through and I never drink one.

Switching from one weapon to another, as in the case of my trip and stun weapons is a serious futile gesture. The way I have determined it to work 100% is this way.
1) press trip..wait to see if trip is activated (usually on second swing after pressing button)
2) look to see if I get a roll for the swing (a lot of times, none.)
3) Once trip is on timer I click on stun weapon to switch.
4) If I am not completely stationary and doing nothing else, it will not switch and i must keep trying. I find going into block mode and jamming the stun weapon will eventually equip it.
5) I then try to stun the opponent by hitting the stun button.
6) as with trip, I have to wait and see if it hits or keep trying.
7) once I have done both of those I will try to go to a normal weapon for DPS
8) this involves waiting a second or two for it to take, while mashing that weapon button and trying not to move at all.
9) this makes combat really stupid as I swing once, sit around and do nothing, swing a second time, (sometimes I get two swings for trip or stun as listed above), then I sit around as I try to get a dps weapon going, get a swing in....then try to switch to a trip weapon since it already reset.


I love going into combat and pressing stalwart defense and CE and then finding out I never activated them...and have to stop everything to make sure I got them on.

combat has slowed to a crawl with my new toon.


What I usually do now is keep a shield on him and a trip weapon at the ready. I leave CE on and when entering combat I try to ignore the game and just watch the buttons and health bar to see if anything is working...and what I need to keep mashing to try to do (trip, stun, stalwart, cure potion).

it has kinda taken the fun out of playing the toon honestly, so I sorta stopped playing more than a dungeon or two every other day until they fix the 'out of sync' part of the game.


and that's my bugs...