A negative impact when attempting to exploit something = legit?
Right, the legit part of the bug and what I have an issue with is that players should NOT even have the option to try to use different ingredients in the UI during a specifically assigned task where they are given exact materials. It's obvious that all kinds of unexpected behavior can happen once you start swapping out materials (after confirming you're going to make it and having the required materials auto-load). Wouldn't exploit something like that if that's what was implied. I'm a game author and QA bug tester IRL.
To add on this: the "Clear" button doesn't work if you used the "Requested Items" one, you have to cancel synthesis altogether.
Saw this same bug again several times more. It was NOT caused by the quest-activator using node the complete the quest. A person would randomly get stranded when everyone else warped out. It happened to me again last night, and I was the one who activated the quest (not even linked with anyone).
I came across a weird situation yesterday where I was done exploring Mhor Donia (spelling?) and my linkshell mate stayed up there to attempt to flag another camp after I left. I headed to Camp Horizon to attempt to complete a leve before the reset today.
With him still in the party, I did the leve where you've got to fight the Wights and noticed that I could not retain TP at all (even a low amount like the 250 you'd need for Second Wind). I'd hit the enemy and the TP would generate but it would decay at an incredible rate; the fights also would not give XP or class rank points until I dropped him from the party (I had initially forgotten he was in party because 30 mins had passed already and I picked up my leves and ran to Horizon).
I'm also FURIOUS when I'm doing combat and the targeting messes up to the point where it autoselects targets depending on the direction you face and you are unable to lock anything (making self healing kinda difficult too). I'm not sure how often I'm hit with this, but I almost expect to get fucked by it every time I kill an enemy an it takes a sec to "die" serverside.
not really a bug but if you start a leve for marks and change classes you will get 0 marks even if you change back.
My experience is at the lv30 camps if someone warps back to a main node (like Horizon instead of Nophica's Wells), the node will disappear and no one else will be able to port. On top of that, me and a friend ported to Black Brush from Nanawa at the exact same time and he was ported and I was not, even though I selected it from the option before the node bugged/disappeared.
If you try to repair something in someone's bazaar and they teleport before you finish it, it cause you to be frozen in the repair animation and causes the other person to crash. I had to alt+f4 to fix my character.
I had a local leve complete itself today. I accepted the leve Under Foot and headed out to camp when i sat down to make the items the materials were already complete.
If you party with an Archer, every time they use Refill, you will get a message saying you loaded your quiver with arrows. Same thing happens when they use Multishot, it states that you knocked an arrow.
It's just a text bug, but it;s annoying.
You're taking the discussion out of context. We are passed this.
bug: The dialog box misspells Crakows as "Crackows" when you equip them. At least for Leather Crakows (Black).
Was hit with the bug where changing your class doesn't actually process fully. The one where it never updates your skill bar, but the game acts like it has and you have to log out to fix it.
Didn't realize it happened and went to gather up four Local Levequests. After accepting all four I check my Journal and two had disappeared. Logging out and logging back in took care of it. Was really confusing at first, until I realized what had happened.
I ran into a bug last night while doing my MRD Rank20 quest. I went to the instance area and it said that I had to reform my group because only one person is able to enter. I wasn't in a PT so I didn't know wtf was going on, but logging out and back in worked :s