Why do we have not relog into Boss Maps when logging off/DC???

Bosses, PQs and expeditions are all instanced in ML and have their own "session". Currently there is no way too add someone back into the "session". We can warp them back into the map but they'll be kind of like a ghost and not actually registered in the instance which can cause all sorts of issues (not being able to exit the map, logging the boss expedition possibly, glitching etc). Even GMs are unable to add themselves into an instance at the moment, so it's really a technical limitation.

Also just curious how do other servers handle people possibly abusing this mechanic, I.e. Zak helm buyers dcing on purpose at the beginning of the run and then relogging back right before it dies to get the drops?

 

Ah makes sense. Yeah ML won't implement SoK so if anyone had a solution to that problem let me know!

 

at first I was thinking about it "why dont come back in map" but when u lear a bit about debuff mechanic (like seduce), and learn a bit about mule-ing you will see this mechanic is pretty unfair

 

Cause then I could just log off and log back in at the end of HT to get a pendant.

 

Maybe there could be a time limit like two minutes to log back in. That would help people who crashed/dropped packets but not let people AFK the whole run.

 

That would work I think... What about the case where you're seduced or something and you're about to die, so you dc/logout in order to not die? Or squads all DC or logout to avoid being sed? (Unlikely but still a possibility for abuse) T.T

 

implement bossing death count (relog) limitations

 

That's exactly what people will do

 

Fairest way to handle this is to treat a log-out during seduce as a death, so when you log back in, you log in dead.

 

I think the concept of relogging into the same boss map is a great QOL for all, especially with the server issues lately.
But the loop holes around it has to be systematically thought-through and dealt with before implementation

 

Great suggestions guys!! Yeah it's just a tricky thing to do with the implementation and the loopholes. If y'all can think of any other edge cases where this could be exploited then let me know, Staff currently has their hands full with other stuff, but I can go ask our dev later if this is even possible on a technical level before moving forward with this conversation lol

 

Only edge case would be if the only bishop in the run disconnects for unexpected reason during seduce.

 

Currently there is not much of a way for us to tell the difference between a "real" disconnect and someone just pulling the power cable on their router and disconnecting on purpose.

 

Maybe DC should kill you. Edit: DC in boss = die but don't lose XP?

 

There’s charms for that buddy

 

It honestly should maintain die and lose EXP just to keep things consistent. Like what's stopping me from nearly dying in a fight against a Spawned boss, just to force crash and then relog in a different channel where I know the boss won't spawn for another hour? Or even in the same channel, knowing that I won't lose EXP?

 

A penny for my thoughts​

Could I suggest bypassing the need for troublesome solutions such as re-registering a player's unique id into a uniquely generated instance of a boss-run thread (which is handled by the client if I'm not mistaken aside from the server-side scripting that is limited)
and re-inserting into the same ongoing instance with all the loopholes that come with it.
and use an approach used in big 3D MMORPGs instead (predefined redistribution of rewards upon successful run upon which all the party agrees before entrance is allowed). altho of course, you could track the
-player id and tie it into a unique ongoing instance so if a player dies and relogs it would -
check if the instance is still ongoing and if it is then re-register and relog right back into it to continue fighting, could also add a -
limit as to up to which point it still is possible to get back in to prevent lazy people, so if the boss is say at 20% life left player won't be logged- in back into that instance but instead outside. otherwise, get back right in there. if the same instance the player was registered with isn't ongoing then the player is transferred out.



Upon player death/dc handle rewards: create value list of all possible drops assign value based on market value or some other kind, check statistics such as boss hp remaining or - damage dealt of a said player before dc/death using this -
data decide which % of potential loot the player deserves, check what the other players in that instance got added to their DB profile as rewards, - assign a value from the list you created-
to each of the rewards and at what tier of % that player deserves they shall unlock to be received. -
offer dcd/died player NPC dialog upon logging within a reasonable time or if the instance is ongoing then upon
an instance being won, the dialog offering the rewards based on the data of their performance and the loot that got dropped and its value in comparison to their performance or- exchange possible rewards for a retry ticket/+1 for the limit of the runs for the day
never give 100% (best value) of the loot just the second or third value is up to you to decide, so to avoid dce'rs trying to monetize easily on those rewards.
perhaps add a way for players to check how many times a player has dcd/died within boss instances with a command such as"playerign check boss run stats" before letting someone join and see
if a player just deliberately dcd if a number exceeds some high number in comparison to the general public on average to discourage deliberate dcing/death.



That way even dcd/due to death players get something based upon how they performed/how much hp the boss had left before the dc or got the chance to try again and forfeit the rewards.
So it's still not worth dcing cause you don't get the good stuff if you dc at 20% or under of boss hp. Still, -
you do get a free retry, or if you dcd/due to death at say 20% of boss hp you don't get the best of the rewards based on the list.-
Still, you get the most like 1 value down from the best that was dropped otherwise. (so not to encourage quitdcing at 21% and still -
getting the best goods) and if you dcd/due to death early on or half through they could get marginally fewer rewards based on the value list so even -
less motivation to do that. and on top of that could add a reputation system for bossing and count the amount of dcing in boss instances -
for other players to see on their profiles. to discourage that behavior even further still.
you can play with the idea however you like to balance it out to fit the bill. anyway, that was you avoid directly dealing with re-inserting players into instances.