pa/eqemu-server
2
0
Fork 0
mirror of https://github.com/EQEmu/Server.git synced 2025-12-14 19:51:29 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Don't remove expedition lockouts from non-members

Browse Source 
Clients still inside a dz after being removed from an expedition
should only ever have lockouts added
This commit is contained in:
hg 2020-06-13 22:44:29 -04:00
parent 17be2bf2f7
commit 006f7bf9e9
1 changed files with 4 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
zone/expedition.cpp
View File

@ -1253,7 +1253,7 @@ void Expedition::ProcessLockoutUpdate(
// if this is the expedition's dz instance, all clients inside the zone need
// to receive added lockouts. this is done on live to avoid exploits where
// members leave the expedition but haven't been kicked from zone yet
if (m_dynamiczone.IsCurrentZoneDzInstance())
if (!remove && m_dynamiczone.IsCurrentZoneDzInstance())
{
std::vector<ExpeditionMember> non_members;
for (const auto& client_iter : entity_list.GetClientList())
@ -1261,17 +1261,12 @@ void Expedition::ProcessLockoutUpdate(
Client* client = client_iter.second;
if (client && client->GetExpeditionID() != GetID())
{
non_members.emplace_back(ExpeditionMember{ client->CharacterID(), client->GetName() });
if (!remove) {
client->AddExpeditionLockout(lockout);
} else {
client->RemoveExpeditionLockout(m_expedition_name, event_name);
}
non_members.emplace_back(ExpeditionMember{client->CharacterID(), client->GetName()});
client->AddExpeditionLockout(lockout);
}
}
if (!remove && !non_members.empty()) // expedition members were already updated in db
if (!non_members.empty())
{
ExpeditionDatabase::InsertMembersLockout(non_members, lockout);
}