wutfor wrote:

My opinion was if it fit within the game mechanics they made, why would I assume I wasn't supposed to do it?

Kiting mobs and FD pulling come to mind.

Roll with it, man. If the devs don't like it, they'll likely change it some day. Like KEI.

I think there's a difference character abilities like those and software features/bugs.  For example, if you kite properly, you never get hit by the mob, but that's very different than never getting hit because a mob is bugged in some way and never even swings at you.

RangerDave wrote:

wutfor wrote:

My opinion was if it fit within the game mechanics they made, why would I assume I wasn't supposed to do it?

Kiting mobs and FD pulling come to mind.

Roll with it, man. If the devs don't like it, they'll likely change it some day. Like KEI.

I think there's a difference character abilities like those and software features/bugs.  For example, if you kite properly, you never get hit by the mob, but that's very different than never getting hit because a mob is bugged in some way and never even swings at you.

In a raid do you guys ever by chance get the message: "Unable to retrieve information on the leader to check permissions. <Player name> could not be invited to join you.'

My logs are on 24/7 and I am a raider, but a search of my logs for 2009 does not find "Unable to retrieve information on the leader to check permissions". Of course, about half the time I am the task leader, so I suspect I'm easy to find.

I'm very familiar with having to find off-line people in the task and boot them before taskadding will work again. It's quite the pain...can't even alpha-sort the list to make it easier.

juhans-DEV wrote:

RangerDave wrote:

wutfor wrote:

My opinion was if it fit within the game mechanics they made, why would I assume I wasn't supposed to do it?

Kiting mobs and FD pulling come to mind.

Roll with it, man. If the devs don't like it, they'll likely change it some day. Like KEI.

I think there's a difference character abilities like those and software features/bugs.  For example, if you kite properly, you never get hit by the mob, but that's very different than never getting hit because a mob is bugged in some way and never even swings at you.

In a raid do you guys ever by chance get the message: "Unable to retrieve information on the leader to check permissions. could not be invited to join you.'

Have not gotten this, ever. Juhans, try to get the level spread bug with the Crystal Core raid perhaps?

The only reason why someone would want a very quick /quit out of a raid instance would be if someone was trying to exploit a raid by adding in people just before a chest drops. Rallos Returns anyone?

danille wrote:

The only reason why someone would want a very quick /quit out of a raid instance would be if someone was trying to exploit a raid by adding in people just before a chest drops. Rallos Returns anyone?

you can taskadd after, why hurry something before hand, when you dont even have to get a lock out on this.

Here is other:

1. Setup a group with 2 players and 2 mercs

2. Get a shared task and get into instance.

3. Taskadd a 3rd player

4. The 3rd player removes himself from task

5. 2 minutes warning for exit task due not meet the minimun requirements appears.

The solution: remove and add the 2nd player. Obviously thats a bug.

tumnayar-MT wrote:

juhans-DEV wrote:

RangerDave wrote:

wutfor wrote:

My opinion was if it fit within the game mechanics they made, why would I assume I wasn't supposed to do it?

Kiting mobs and FD pulling come to mind.

Roll with it, man. If the devs don't like it, they'll likely change it some day. Like KEI.

I think there's a difference character abilities like those and software features/bugs.  For example, if you kite properly, you never get hit by the mob, but that's very different than never getting hit because a mob is bugged in some way and never even swings at you.

In a raid do you guys ever by chance get the message: "Unable to retrieve information on the leader to check permissions. could not be invited to join you.'

Have not gotten this, ever. Juhans, try to get the level spread bug with the Crystal Core raid perhaps?

Yes, I am trying to get the level spread bug to occur in Crystal Core.  Any more information on how to make this possible would be greatly appreciated.

Thanks.

navi7512 wrote:

Here is other:

1. Setup a group with 2 players and 2 mercs

2. Get a shared task and get into instance.

3. Taskadd a 3rd player

4. The 3rd player removes himself from task

5. 2 minutes warning for exit task due not meet the minimun requirements appears.

The solution: remove and add the 2nd player. Obviously thats a bug.

 

Mercs do not count as a player for the purpose of maintaining a task zone, but do count for the purpose of requesting one.  Further, whether you got enough players to maintain a zone is only checked when someone is added or dropped.  So it goes like this:

2 player + 2 mercs = Can get expedition, cannot maintain expedition (but this is not checked until someone else is added/removed)

Add 1 player, now you have 3 players so now you can maintain the task.

Drop 1 player, now you have 2 players and now you cannot maintain the task.

The mercs don't matter at all for the calculation on maintaining.  I'm pretty sure you can dismiss your mercs immediately after you got the expedition with 2 people and it wouldn't have any effect. 

juhans-DEV wrote:

tumnayar-MT wrote:

juhans-DEV wrote:

RangerDave wrote:

wutfor wrote:

My opinion was if it fit within the game mechanics they made, why would I assume I wasn't supposed to do it?

Kiting mobs and FD pulling come to mind.

Roll with it, man. If the devs don't like it, they'll likely change it some day. Like KEI.

I think there's a difference character abilities like those and software features/bugs.  For example, if you kite properly, you never get hit by the mob, but that's very different than never getting hit because a mob is bugged in some way and never even swings at you.

In a raid do you guys ever by chance get the message: "Unable to retrieve information on the leader to check permissions. could not be invited to join you.'

Have not gotten this, ever. Juhans, try to get the level spread bug with the Crystal Core raid perhaps?

Yes, I am trying to get the level spread bug to occur in Crystal Core.  Any more information on how to make this possible would be greatly appreciated.

Thanks.

Well, we have a raid, maybe 40-50ish people, we get the task, we go into the instance and start clearing trash, someone camps out to reboot computer or whatever. Someone else logs on after we've already started and wants to join raid, can't add them till the first person that is rebooting comes back or if I taskremove the offline person. That's about all there is to it, I don't know what else would be different or would not give you the bug. Maybe it is a random occurence that happens more often than not, who knows, I've seen it many many times throughout many different task raids.

tumnayar-MT wrote:

Well, we have a raid, maybe 40-50ish people, we get the task, we go into the instance and start clearing trash, someone camps out to reboot computer or whatever. Someone else logs on after we've already started and wants to join raid, can't add them till the first person that is rebooting comes back or if I taskremove the offline person. That's about all there is to it, I don't know what else would be different or would not give you the bug. Maybe it is a random occurence that happens more often than not, who knows, I've seen it many many times throughout many different task raids.

Pretty sure anybody who is not online is considered to be a level 0, or at least low enough that you will never meet the 15 level requirement.  There's nothing random about it.  It always stops you from adding someone if you got someone not currently online in the expedition.

AutomaticWarrior wrote:

tumnayar-MT wrote:

Well, we have a raid, maybe 40-50ish people, we get the task, we go into the instance and start clearing trash, someone camps out to reboot computer or whatever. Someone else logs on after we've already started and wants to join raid, can't add them till the first person that is rebooting comes back or if I taskremove the offline person. That's about all there is to it, I don't know what else would be different or would not give you the bug. Maybe it is a random occurence that happens more often than not, who knows, I've seen it many many times throughout many different task raids.

Pretty sure anybody who is not online is considered to be a level 0, or at least low enough that you will never meet the 15 level requirement.  There's nothing random about it.  It always stops you from adding someone if you got someone not currently online in the expedition.

When you say expedition, what are you referring to?

juhans-DEV wrote:

AutomaticWarrior wrote:

tumnayar-MT wrote:

Well, we have a raid, maybe 40-50ish people, we get the task, we go into the instance and start clearing trash, someone camps out to reboot computer or whatever. Someone else logs on after we've already started and wants to join raid, can't add them till the first person that is rebooting comes back or if I taskremove the offline person. That's about all there is to it, I don't know what else would be different or would not give you the bug. Maybe it is a random occurence that happens more often than not, who knows, I've seen it many many times throughout many different task raids.

Pretty sure anybody who is not online is considered to be a level 0, or at least low enough that you will never meet the 15 level requirement.  There's nothing random about it.  It always stops you from adding someone if you got someone not currently online in the expedition.

When you say expedition, what are you referring to?

He means TASK (alt Q window), not expedition (alt Z window).

Expeditions have no problem like this.