Sur les forums officiels US :
Poster : amlug amlug is offline
The Lord of the Rings Online Team
Turbine, Inc.
Join Date: Jan 2007
Posts: 20
Re: AAAH! Raid lock
_________________________________________________________
Quote:
Originally Posted by Zanzopan View Post
Before the patch, whoever entered the instance first would set the raid locks and everyone else would inherit them. If the person first had none, then everyone would have their reset. If they had 2,5,10 (not sure how that would happen), then the group would get 2,5,10.
Now, everyone has to have the exactly the same raid locks (or none, and will inherit everyone elses). Even if one person has some of the raid locks everyone else has (but not all) they can not enter. So if 4 of the group has 1,2,5,6,7,8 locks on, one has none and one has 2,5,6 then the 4 with the same can enter, the one with none can enter but the one with 2,5,6 can not despite them having only ones that the group has (but not all). They need to fix it so any one with the same locks can enter a instance as long as they share all of the ones with the instance lock setter.
_______________________________________________________
So just wanted to weigh in here. We have been looking at raid locks and constantly trying to figure out the sweet spot here so that they work for everyone. Coming soon to a patch near you, the leader will be the one who controls the raid locks and any player who has the same locks, no locks, or a smaller sub set of the leader's locks will be allowed to enter and will gain the leader's locks.
So in the above scenario, if the leader has 1,2,5,6,7,8 and someone wishes to join the raid and has 2,5,6 - then they will be able to join and they will be upgraded to the leader's locks so their locks will also be 1,2,5,6,7,8. However in this scenario, if someone wishes to join and has 1,2,3 - then they will not be able to join since they did a part of the instance that the leader has not yet done.
I hope this helps a bit. This will be coming very soon and sorry for any confusion this may have caused. We continue to evaluate the raid locking systeam and are going to do our best to make sure that it is as easy to work with as possible on your end!


