![]() ![]() If the majority of the group votes “yes”, then you get the rewards for this phase and are booted out of the raid. So logically every MMO-player assumes that you can start those phases seperately, since you do NOT achieve all 3 of those item levels in the same week, if you are not hard-cashing.Įvery character can only claim rewards ONCE per week from the Argos raid and whether you recieve rewards, after let’s say phase 1, is decided by a vote. The Argos Raid consists of 3 phases, each one has a higher item level requirement (1370, 1385 and lastly 1400) to even start the encounter. I want to clarify, for a better understanding of why I have an issue with this: ![]() Why can I not start at phase 3 argos, when I already ran phase 1 and 2 a few days ago in the same week?Īm I the only one whos is frustrated about this design choice? When I run a 10-bosses raid in WoW and we only get to boss 7, then we start at boss 7, when we reenter a few days later. Is it really that hard to program these raids so that you, as in your character, can start where it left off? When I run 2 phases and have to leave because its midnight and I have to work the next day, why do I have to run those 2 phases again the next time? Why cant I start at phase 3, when its still in the same week?Ĭan I please have an official answer as to why this is programmed in this anti-player way? This is frustrating. This basically means that every time a group decides to leave the raid for whatever reason (personal, family, work, whatever), you have to run ALL of the phases again from the beginning. This is seriously bad design, I cannot think of any positive reason here. Turns out I cant enter the raid anymore, since the group I ran phase 1 with decided to claim the rewards and now I am locked out of the raid. I reached 1385 today, so I wanted to run phase 2 to get the new rewards. I didnt think I would be getting item level 1385 this week, so I ran argos phase 1 before the weekend. I had item level 1374 or someting at the beginning of the weekly reset.
0 Comments
Leave a Reply. |