![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Actual Kara recap next post, when I get home with my list of character names.
PUBLIC SERVICE ANNOUNCEMENT and general whinge:
As per this informative thread, characters are "saved" to particular higher-level instances which reset once a week, when they enter the instances and kill the first boss mob there.
Extended quote (in italics) from reply in that thread:
"This is done for two reasons:
1. To save the instance, so that slower, more casual guilds have time to work through them... as opposed to normal instances which reset when vacant for 2 hours (or something like that).
2. To stop guilds from farming 500 pieces of loot at week.
...If you look at the entry in /raidinfo, it has an instance id#.
If you enter an instance, and the raid you are with killed a boss yesterday, but you weren't there. You do not get saved simply for entering the instance [[ETA: This is apparently not true. You DO get saved for entering the instance, or it's as soon as you kill trash.]]... As soon as you kill a boss with them however, you are saved to their instance ID.
You could join another raid, and go to the instance. When you zoned in, you would be in 1 instance, and they would all be in another. Or, if you entered before them, they would enter your instance. Any boss you killed with the other [first] raid would be dead already. Any boss you then proceeded to kill would be dead when members from the first raid you entered with came back."
Karazhan (Kara, KZ) resets at 5am Tuesday morning. This means that if you go with someone else's guild on Saturday, you can't go with your own guild on Sunday morning (unless they enter after you, and then they get the instance that you've already partly/fully run with other people.)
Now, you wouldn't think this was a big deal, but when nearly half our guild's raiding force doesn't notice the text line when they enter KZ (it reads "this instance will reset in __ days __ hours") or the line that appears when you kill a boss saying "You are now saved to the instance" and then goes and saves to someone else's instance the night before we have a scheduled Kara run, it makes things suck.
It makes Enh'ar a very unhappy shaman, too, when she voluntarily passed on equipment (which was an upgrade) to give to another guildie for whom it was MORE of an upgrade, because Enh'ar was thinking of the raid team as a whole, not only of herself, and when that guildie takes the equipment they were given and the equipment they rolled for as part of our guild's raid team, and goes to play on someone else's raid with their new stuff.
Of course, there's a law that you should never attribute to malice what can be explained by sheer stupidity, and perhaps that should be our guild motto.
PUBLIC SERVICE ANNOUNCEMENT and general whinge:
As per this informative thread, characters are "saved" to particular higher-level instances which reset once a week, when they enter the instances and kill the first boss mob there.
Extended quote (in italics) from reply in that thread:
"This is done for two reasons:
1. To save the instance, so that slower, more casual guilds have time to work through them... as opposed to normal instances which reset when vacant for 2 hours (or something like that).
2. To stop guilds from farming 500 pieces of loot at week.
...If you look at the entry in /raidinfo, it has an instance id#.
If you enter an instance, and the raid you are with killed a boss yesterday, but you weren't there. You do not get saved simply for entering the instance [[ETA: This is apparently not true. You DO get saved for entering the instance, or it's as soon as you kill trash.]]... As soon as you kill a boss with them however, you are saved to their instance ID.
You could join another raid, and go to the instance. When you zoned in, you would be in 1 instance, and they would all be in another. Or, if you entered before them, they would enter your instance. Any boss you killed with the other [first] raid would be dead already. Any boss you then proceeded to kill would be dead when members from the first raid you entered with came back."
Karazhan (Kara, KZ) resets at 5am Tuesday morning. This means that if you go with someone else's guild on Saturday, you can't go with your own guild on Sunday morning (unless they enter after you, and then they get the instance that you've already partly/fully run with other people.)
Now, you wouldn't think this was a big deal, but when nearly half our guild's raiding force doesn't notice the text line when they enter KZ (it reads "this instance will reset in __ days __ hours") or the line that appears when you kill a boss saying "You are now saved to the instance" and then goes and saves to someone else's instance the night before we have a scheduled Kara run, it makes things suck.
It makes Enh'ar a very unhappy shaman, too, when she voluntarily passed on equipment (which was an upgrade) to give to another guildie for whom it was MORE of an upgrade, because Enh'ar was thinking of the raid team as a whole, not only of herself, and when that guildie takes the equipment they were given and the equipment they rolled for as part of our guild's raid team, and goes to play on someone else's raid with their new stuff.
Of course, there's a law that you should never attribute to malice what can be explained by sheer stupidity, and perhaps that should be our guild motto.
