Showing Posts For Tom Stone.3190:
bugged on 5 different server ip’s – glitches every time in the same place – NPC stops moving towards first signal beacon preventing the event chain from progressing.
Same here, seems accounts got un-linked for some reason, received email, all titles/achievements from gw1 legacy have been removed, my account from gw1 calculator:
Still broken – gw2community did 4 attempts yesterday and another 4 today – all bars were broken, shaterer still took off and didn’t award the achievement – every time we got points toward no fly zone broken bars.
either extend the time between break bar and fly animation or shorten the break bar to show actual time needed…
participated in 3 teams, got reward from 1, 2 others came up empty – gl&hf
Anyways, to everyone complaining, get the 100 grabs and 300 carries achievements done and if you still don’t have Crabtactular done, then that’s the time to complain, it’s too hard.
Thats exacly why I am complaining I don’t have much of a problem winning or scoring enough grabs/caries for other achievements, I just don’t see a point in making an achievement – which is by definition something someone should be able to DO – that requires more luck than actual skill.
Purely random achievement – it takes 1 afker on 1 player with more than 2 brain cells to prevent you from obtaining it, and convincing 8 RANDOM people to stop fighting and help each other gaining it is even less possible than obtaining it via lag spike (which is by the way the only way people I know got it).
If even players from top 10 achievement leaderboards say they only got it by luck rather than skill – then something is surely wrong.
This should definitely be implemented – its hard enough already to maintain a guild whose members can represent 4 other guilds, ending in ghost-town type of communities that only a handfull of people play in…
As everyone has noted, this issue should be resolved now. Unfortunately, you may have experienced a roll back due to this issue – our programmers are looking into this to prevent it from happening in the future.
We apologize for the inconvenience, and thank you for your understanding!
Rollback? This is some kind of grim joke – i’m missing 11 ecto and an entire daily fractal reward (including infused ring) due to this “issue” – because the login servers went down when I was selling/salvaging my drops…
The location where you camp is basically anywhere @ swamp – the event indicator should chjange from “Swamp lies dormant” to whatever pre event just had started. The point is – it doesn’t and the 3 portal spawn points for pre events are empty.
Aurora Glade haven’t seen Behemoth since before Halloween. People from my guild (including me) have been camping in the swamp for days now, both idle and doing various things (spawning fleshreavers, killing portals, the usual stuff) and nothing sem to trigger the pre-events for the boss, while other world bosses on lvl 1-15 locations have ben triggering normally (i pass near the maw once every day and there is an event there almost every time).
So, if a dev is reading this and this is somehow NOT a bug – at least let us know what is the trigger for the behemoth event chain – is it time-based or some other events must happen for it to launch?
Can the devs confirm on that last one? About 5 people from my guild are camping in the swamp (we take shifts) for nearly 3 days now and we havent seen him even once (Aurora Glade server)…
Guys – this thing can be done in about 30 minutes solo – dont expect it to have high reward rate because it would ruin the economy… again.
I couldn’t open the chest at my first attempt – I suppose it has to do something with me opening (for the first time also) a chest in the clocktower?
Ok, the update is fun, but I wonder what about the “old” Black Lion Chest tonics (the BLC before a few updates didn’t drop mystery tonics but specific-creature-transformation tonics instead. Those tonics cant be traded (account bound) and there are people who still has loads of them – is there a chance we could transform them into mystery tonics instead? Firstly – it will save the space, secondly, we will have a way of re-purposing the ones we don’t really need.
After a few tries he is no more a problem – and if you really cant manage to pug him, just get yourself a decent enough guild. At this point my guildies are able to zap him with any given class setup in a matter of 10-15 minutes.
So, I’m now supposed to play with a watch in hand, checking my time, and if somehow its too fast just /dance before entering the final boss room? No offence, but this is plain stupid. I understand DR for people that do the same path in a dungeon twice (or more) per day, to get tokens, but why are we beong punished for being organized and good at what we do inside? In my opinion there should be absolutely NO DR for EACH PATH that is being done for the FIRST TIME in a day, and the timer should reset just as the daily achievements do. And I believe that is what devs intended to do (according to the latest patch notes). Unfortunately, it doesnt work as it should – and I can only hope for a fix soon…
I do all dungeons with my guild, mostly in the exact same group (give or take one person). The rewards vary between the group members even if we do exacly the same dungeons in exacly the same time intervals.
Yesterday:
TA:
Up: 60
Forward, forward: 60
Forward, up: 45
ETA 3 paths 4,5h
Afterwards, CoF, Magg path: 45 tokens, 45 mins run.
Today:
Up: 60
Forward, forward: 60
Forward, up: 45
ETA all paths 4h
Srsly fix this…
(edited by Tom Stone.3190)
Ok, here is how it looks for me:
Today I wanted to look how the new dungeon system works. And it doesn’t (still) work as developers intended. I dont actually like grinding trough the same place all day long, so the change in reward system was (for me) a thing to look forward to. In theory, doing all 3 paths in a dung per day will be enough to get every item I want in a reasonable amount of time. Well, that was the theory…
At my first run of Twilight Arbor I was in the dungeon for about 30 seconds. Candrzasty mentioned my case in his post – I joined a group that was already fighting the last boss. I wasnt even able to reach the boss, still, I received full dungeon completion reward (60 blossoms, 29 silver).
Then I did two other paths in TA – forward, forward and forward, up. The first one gave me full reward, the second one only 45 blossoms and 19 silver. Since I actually didn’t participate in the first patch, I decided to help the rest of my team (most of them weren’t doing the one I did). So we went to the “up” path and I received 15 Blossoms and about 6 silver. According to the dev notes for today’s update I should have received 3×60 blossoms for the 3 first paths and 20 blossoms for the patch that I did twice – simple mathematics says I’m missing 20 blossoms. As I mentioned – it doesnt matter much for me in today’s case, since my first run was about 30 seconds, but there were people with me who also received lower rewards – for no reason whatsoever.
After my “short” (roughly 4 hours) adventure in TA I decided to change dungeon – since CoF was supposed to be repaired, it became my next target. We did the Magg way, which was fortunately fixed against exploiters, and after less than an hour I received my reward – 45 Charr Carvings and 19 silver.
Now, my question is – where is the rest of the tokens that I was supposed to receive after finnishing this path for the first time in the day? Am I supposed to spend a fixed amount of time in certain dungeon to receive full reward? Or maybe I need to kill every single mob? Or I should be in a certain party of people? Because now the reward system does NOT work as it was intended and claimed in the developer update notes – its not even close.
Just a little bug report:
Superior Sigil of Energy and Major Sigil of Energy have exact same in-game descriptions: restores 50% endurance on weapon swap in combat (9s recharge). Didn’t entirely test the cooldowns, but they seem to work the same as well, while the Superior costs 55+ silver and the major one is 2 silver on Trading Post…
3040:1002:3:1930:101
same problem here, and it worked just fine couple of days ago (one update earlier).
(edited by Moderator)