I guess well now have 15 people with bluebell chaingun turrets sitting near an arms dealer, shooting around, waiting till he lagcrashes and take his stuff.
' Wrote:I guess well now have 15 people with bluebell chaingun turrets sitting near an arms dealer, shooting around, waiting till he lagcrashes and take his stuff.
That's kind of clever in a :nono:sort of way. With that in mind, how come Bluebells weren't fixed like the other chain guns?
My thought is that this is a great idea in concept, but I'm not sure how well it will work in practice. I say allow requests for reimbursement while it's in a beta type stage.
Eh, I live very far from the server.
Often I have a ping around 200 or more.
I do appreciate the work being done to deter 'cheaters' that avoid pirate RP or whatever sick ideas you think players would conduct the "F1 Maneuver" for, but I cannot fully support something like this coding to be tested on a live server as I do lag disconnect several times a day, granted I often do not lag disconnect near other players on characters with RP cargo like my guard pilots I have aboard my vessels or real cargo such as my 9 million credits worth of deuterium (foturnate for me). But I do know others that have the same lag problem and their characters may fly into areas where the lag disconnect situation could be an issue. If you will re-imburse wrongfully lost cargo, that's great. But you will be dealing with that in place of sanctions? * question because you may still get sanction reports for F1 in RP interactions?
The notification of a player disconnecting by means of F1 is a great Idea. Loosing cargo is also an interesting approach, although I think it is not the best approach to the problem unless it can be perfected as players may recieve a rather harsh punishment for a crime they did not commit.
Now the problem I see with that is possible people removing their network cable or turning off their wireless card in place of hitting F1 in order to avoid the punishment and exploit the coding you worked on. Can your coding compensate for this? Or can it not distinquish between real lag or someone trying to fake a lag.
In general, this just seems like it would be a good idea, but it is too controversial to implement as a standard server operation and really unecessary as it will not always target the cheating players. I do not see other game developers putting in software on live servers that threatens to punish the innocent players.
Thanks for this awesome new plugin, Cannon. I really love it. It'll make things much easier...
Also, why are all of you complaining? Sure, it may be tough for people with laggy connections when they are trading, but unless you got some really screwed up connection it shouldn't be that bad (and if it really is - just ask Cannon if he might whitelist you so the plugin won't take away your cargo, maybe he'll do it:)). Combat ships aren't affected at all by this - actually, if you lag out in a battle, people might even refrain from targetting you when they get the green message telling them you lagged out/F1'd.
Again, I simply ask it to only show a msg when F1ing, so the players around will take care of "killing" the player in less than a minute (We have lived with that one minute thing for a year, never had any problems nor complains [Except when exceeding 59 seconds])
As mentioned, we doubt the plug-in will always be able to make a distinction between a F1 and a disconnect. Also, those victims will not be able to create SS and evidences to claim back what has been lost as everything happens to quickly sometimes.
It used to be innocent until proven guilty, now I feel as if it is only Guilty. since I see no way to prove someone's innocence.
--
As an alternative to reduce the number of rule breaking repports, best would be to make an anti-swearing plug-in, as you have in many FPS games with punkbuster. Two/three swears (warning in shiny letters for the firsts ones) and you're booted for X days and fined, etc. And this plug-in can't generate more harm than good, since everyone would get one warning, then bam! out!. Having victims in this case is impossible, since there is no way to "accidentally" swear twice... There is no special key you could hit involuntarily that would make your char swear and your computer can't decide by itself to start swearing in chat.
What kind of rules violation do you receive the most? Insulting and swearing of course.
' Wrote:Again, I simply ask it to only show a msg when F1ing, so the players around will take care of "killing" the player in less than a minute (We have lived with that one minute thing for a year, never had any problems nor complains [Except when exceeding 59 seconds])
As mentioned, we doubt the plug-in will always be able to make a distinction between a F1 and a disconnect. Also, those victims will not be able to create SS and evidences to claim back what has been lost as everything happens to quickly sometimes.
It used to be innocent until proven guilty, now I feel as if it is only Guilty. since I see no way to prove someone's innocence.
--
As an alternative to reduce the number of rule breaking repports, best would be to make an anti-swearing plug-in, as you have in many FPS games with punkbuster. Two/three swears (warning in shiny letters for the firsts ones) and you're booted for X days and fined, etc. And this plug-in can't generate more harm than good, since everyone would get one warning, then bam! out!. Having victims in this case is impossible, since there is no way to "accidentally" swear twice... There is no special key you could hit involuntarily that would make your char swear and your computer can't decide by itself to start swearing in chat.
What kind of rules violation do you receive the most? Insulting and swearing of course.
Actually, whilst you cannot profane twice in the same sessions accidentally, unless really, really unlucky, perhaps it resets after a time?
I know hailing dead_shot has proven to be a problem for a few.:lol:
imo - the plug in is good for the greatest part as it is now.
that is ... if :
- unintentional disconnects are not affected too much
- the time counts that a player actually left the game, NOT when the ship leaves the game-
- its only cargo
basicly everything that was desribed...
now - if possible, i d back up to exclude certain ships ( of if that doesn t work .... certain IDs from it ).
- miners for example are meant to not only spend most of their time in space, but are also rather likely to log out/in there ... intentionally.
- the barge should be excluded, cause that ship is simply not supposed to dock but it is supposed to log in space
what we must be aware of is:
- players WILL find their ways around. - so if the goal is to get rid of the rule.. i do not think that it will succeed. a player that values his cargo higher than a simply pirate RP request will also risk to pull his cable and reboot.
- we might also need to install a piracy limit ( which we don t "really" have ) - in many cases i don t like F1 traders - but when a trader is asked for a rediculous amount of money like 5 million or more on a run that does the same amount or even less, then i actually DO symphasize with a F1 trader. - this plug in sanctions one side only right now.
it doesn t really need a rule for that, but a guideline. - the argument "but you do 100 million in one hour" is as valid as saying "i can attack your battleship with 12 bombers and consider it fair, cause you are supposed to fly with escorts" ( or in other words, totally void )
all in all - the plug in is good. - really....
.... but it won t solve any problems, i believe. i wouldn t say that it creates more. - but i think it only shuffles the problems around a bit. before we had annoyed and frustrated pirates. now we get annoyed and frustrated traders.
and EVERY trader that disconnects will claim by default that it was no F1 but a true disconnect - and will claim that he was punished unfairly. - just as none of the F1 traders so far would openly say that they just intentionally did the F1. ( unless they re really dim )
Not sure I like it. Too cut and dried for me.
Having said that, if F1's are that numerous and it's felt by the powers that be that there is a need for this, then give it a go for a month and then analyze the result.
I for one will be screen shotting every cargo, every run, just in case. Getting stuck in a dock sequence at the end of a particularly long and risky run is no fun what so ever. Even less now so my opinion is, for what it's worth, suck it and see.