As you know im all about trying to stop grief play, i hate it.
So after doing the logging accounts to insta disconnect fix i wanted to work on the force shut down fix.
I thought this would be harder. but it was actually really saimple. It was identifying where in the code it actually happens.
This fix is for the Brown Grief of ending the task via task manager. You cant Alt+F4 while brown as it wont end the process, so it has to be done manually via task manager.
What i have now done is linked the players BrownTime to the client disconnect checks in the mirconnection process.
I did a video as you all know i like my videos ^^
As you can see, the Brown players game closes as expected but the server still keeps the players connection alive all thew time he is brown, which left me free to kill him, he also drops aswell while brown so there is the risk of dropping.
This has caused quite a controversy on my view of PK but regardless of your view, the ability to FORCE disconnect your client should not be an option.
I have linked this to the BrownTime and Conquests where it is used maliciously, this will not affect legitimate players playing on the server and lagging out.
in Server>MirNetwork>MirConnection.cs
find the Process()
this tells the server to instantly disconnect any client that is no longer connected.
this is what i changed it too.
What does this actually do?
The first one is easy, if your brown you will remain in game untill you are no longer brown, or dead if you force shutdown.
the second one:
Everytime you attack something or are attacked by a player or a monster you set a timer known as the Globals.LogDelay (default 10 seconds)
This stops you logging out for 10 seconds ( players bypass this by logging into the same account, which i have fixed, but also by force closing down the client)
If you lag out, you still stay connected and then you disconnect once the server stops recieveing communication from the client.
This will now keep the "player" connected on the server untill the timer is up, eliminating the force shutdown bypass.
i linked it to WarZones because its common to see player force quit to avoid dying during a sabuk wall conquest/ war
this will not affect guild wars. players will still be able to use this method untill i find a suitable solution.
So after doing the logging accounts to insta disconnect fix i wanted to work on the force shut down fix.
I thought this would be harder. but it was actually really saimple. It was identifying where in the code it actually happens.
This fix is for the Brown Grief of ending the task via task manager. You cant Alt+F4 while brown as it wont end the process, so it has to be done manually via task manager.
What i have now done is linked the players BrownTime to the client disconnect checks in the mirconnection process.
I did a video as you all know i like my videos ^^
As you can see, the Brown players game closes as expected but the server still keeps the players connection alive all thew time he is brown, which left me free to kill him, he also drops aswell while brown so there is the risk of dropping.
This has caused quite a controversy on my view of PK but regardless of your view, the ability to FORCE disconnect your client should not be an option.
I have linked this to the BrownTime and Conquests where it is used maliciously, this will not affect legitimate players playing on the server and lagging out.
in Server>MirNetwork>MirConnection.cs
find the Process()
this tells the server to instantly disconnect any client that is no longer connected.
this is what i changed it too.
What does this actually do?
The first one is easy, if your brown you will remain in game untill you are no longer brown, or dead if you force shutdown.
the second one:
Everytime you attack something or are attacked by a player or a monster you set a timer known as the Globals.LogDelay (default 10 seconds)
This stops you logging out for 10 seconds ( players bypass this by logging into the same account, which i have fixed, but also by force closing down the client)
If you lag out, you still stay connected and then you disconnect once the server stops recieveing communication from the client.
This will now keep the "player" connected on the server untill the timer is up, eliminating the force shutdown bypass.
i linked it to WarZones because its common to see player force quit to avoid dying during a sabuk wall conquest/ war
this will not affect guild wars. players will still be able to use this method untill i find a suitable solution.
Last edited: