Right now this seems to be a huge problem, causing not only sanctions, but other random drama. I know it is possible to have the server change a players ship inbetween zones, such as during a jump hole or jump gate. When a player dies to pvp why not have a server script log the system, and to change the players ship into a escape craft or camera ship. Also add a server command /forgive, where the person who kill that individual can forgive them and when they dock or re-enter the system they will have their ship back, or after 4 hours.
I think the current system is fine. Common sense is finding out the server rules, knowing them, and obeying them.
Such complicated game mechanics leave too much room for error. Besides, even if you die in one system, you can still fly that character in another system.
' Wrote:Right now this seems to be a huge problem, causing not only sanctions, but other random drama. I know it is possible to have the server change a players ship inbetween zones, such as during a jump hole or jump gate. When a player dies to pvp why not have a server script log the system, and to change the players ship into a escape craft or camera ship. Also add a server command /forgive, where the person who kill that individual can forgive them and when they dock or re-enter the system they will have their ship back, or after 4 hours.
It just seems like common sense.
That's just a partial solution. Lot of re-engaging is done by switching characters.
' Wrote:I think the current system is fine. Common sense is finding out the server rules, knowing them, and obeying them.
Such complicated game mechanics leave too much room for error. Besides, even if you die in one system, you can still fly that character in another system.
Just looking at the sanction list it seems like a ton of time and effort is being put into try to police all these re-engagment issues. So using a server side solution to make the whole process simpler for vets and massively for new players would be great for Disco. Disco could use some more people, less rooks being scared away would help that.
You're free to design and code a server side solution for the issue. If our development team or administration team felt it was a big enough issue, they'd devote their time to finding a server side solution. That said, they may be doing just that or they may not deem it that big of an issue.
Either way, there isn't really a point in debating about it here on the forums.
Just don't forget you would have to figure out a way to apply that solution to ALL accounts of the re-engager. EDIT: You also have to consider that some people play with a router and their family members, so they have same IP.
While some of his ships might be transport ones, and therefore, will not fall under that rule.
+ training duels, of course.
About "forgive" system - blue message often incorrectly shows the player that killed you. + teamkills (both intentional and unintentional), etc.