Jump to content
Forum Shutdown 28/7/2023 Read more... ×
Sign in to follow this  
InfinityIncarnate

Game Crash/Computer Crash - Flagged for unsporting behaviour!

37 comments in this topic

Recommended Posts

Players
127 posts
3,089 battles

Hello everyone.

So my computer just crashed while it was loading into a match, more specifically, it was a BSOD. My computer automatically rebooted and went back into windows, and I get the game client loaded again.
I didn't get an option to join the battle again, further more, only moments later I get flagged for unsporting behaviour, which is complete BS, the game client should be able to tell the difference between closing the game client (leaving/quitting the match) and force closing, including game client crash (which doesn't exclude a computer crash). WG should definitely change how they go about this, and punishing a player for a game crash is not acceptable!

/Inc.

  • Boring 2

Share this post


Link to post
Share on other sites
[TORAZ]
Beta Tester
15,786 posts
26,801 battles

No, it should not. It'd be too easily exploitable otherwise.

Besides, you're not being penalized. Being pink is a warning, actual punishment comes with being orange.

  • Cool 2

Share this post


Link to post
Share on other sites
Players
127 posts
3,089 battles
10 minutes ago, El2aZeR said:

No, it should not. It'd be too easily exploitable otherwise.

Besides, you're not being penalized. Being pink is a warning, actual punishment comes with being orange.

How exactly would it be exploitable, if the game client could tell the difference between closing/quitting the game through the normal method and forcing closing, including game client crashes?

 

I am being punished, because now I have to play cautios, and try to avoid anything that could cause it to escalate, I'm just not being punished severely.

Consider what would happen if the game client/computer crashed again while this warning status was still in effect, it would escalate it, and then I would suddenly get penalized more severely, and for what, my computer crashing!

Hence why they should go about it differently, because computer and game client crashes can happen, and as players, it's not something we're in control of when it happens.

Share this post


Link to post
Share on other sites
[RJCTS]
Players
1,568 posts
10,303 battles

On this way or that way you put your team on disadvantage. Someone has to pay for that and unfortunately it was you this time.

If you do not have such crashes often then you are fine, but if you have them often maybe check whats going on with PC.



Cheers

  • Cool 5

Share this post


Link to post
Share on other sites
[PUPSI]
Freibeuter
15,160 posts
Vor 2 Minuten, InfinityIncarnate sagte:

How exactly would it be exploitable, if the game client could tell the difference between closing/quitting the game through the normal method and forcing closing, including game client crashes?

do a pc crash manually (reboot button) and you can leave every game without penalty...

  • Cool 1

Share this post


Link to post
Share on other sites
[SYTHE]
Players
55 posts
35,457 battles

I guess we have all been there.  It is appealable, but why bother??

Share this post


Link to post
Share on other sites
Players
127 posts
3,089 battles
9 minutes ago, Boris_MNE said:

On this way or that way you put your team on disadvantage. Someone has to pay for that and unfortunately it was you this time.

If you do not have such crashes often then you are fine, but if you have them often maybe check whats going on with PC.



Cheers

But that wasn't me, I didn't put the team at a disadvantage, it's not my fault that the computer crashed, and because the game did not allow me to reconnect to the match when I got back into the game, then it was actually partially at fault to.
I usually don't have any issues of this sort, but thats besides the point - I didn't leave the match, my computer crashed, which I had no control over, so I don't think that it's is reasonable to punish with a warning.

 

11 minutes ago, Klopirat said:

do a pc crash manually (reboot button) and you can leave every game without penalty...

How a pc is shutdown is logged, so if you manually shut it off/restart it, it will be reflected in the pc logs. And guess what, I'm sure that it could be made to be checked if the game wasn't shutdown by normal means, basically if the game client wasn't shutdown normally, it could be made to check those logs.

 

12 minutes ago, bigredg said:

I guess we have all been there.  It is appealable, but why bother??

It may be that it's appealable, what I'm talking about that it shouldn't happen in the first place. In these cases, warnings and punishments, should only be issued when the rules are intentionally being violated, not when the computer or game client crashed.

  • Boring 1

Share this post


Link to post
Share on other sites
[TORAZ]
Beta Tester
15,786 posts
26,801 battles
22 minutes ago, InfinityIncarnate said:

How exactly would it be exploitable, if the game client could tell the difference between closing/quitting the game through the normal method and forcing closing, including game client crashes?

 

Are you actually that naive? There are tons of methods to forcibly cause a program to crash.

 

And you should be cautious regardless, as such it shouldn't have any impact on your game experience at all.

Unless ofc you normally aren't, but then you deserve to be penalized.

Share this post


Link to post
Share on other sites
Players
127 posts
3,089 battles
4 minutes ago, El2aZeR said:

 

Are you actually that naive? There are tons of methods to forcibly cause a program to crash.

 

And you should be cautious regardless, as such it shouldn't have any impact on your game experience at all.

Unless ofc you normally aren't, but then you deserve to be penalized.

I'm not naive by the slightest, I know there are methods to force a game to close, if you force a game to close, then it will be logged by the computer. Forcing a game to crash is completely different matter, because forcing a game to crash would be to force it stop responding or force it to close unexpectedly. I don't know what you are referring to when you're saying tons of methods to forcibly cause a program to crash, because force closing and forcing a crash are two completely different things.

Don't think you're getting what I'm talking about, when playing normally I do try to avoid violating the rules, but with this warning status in effect I have to play extra cautiosly, so it should be obvious that it would impact my game experience.

Share this post


Link to post
Share on other sites
[TORAZ]
Beta Tester
15,786 posts
26,801 battles
2 minutes ago, InfinityIncarnate said:

force closing and forcing a crash are two completely different things.

 

I am well aware. Doesn't make it any less easy.

Also WG is allowed to read Windows logs now?

 

4 minutes ago, InfinityIncarnate said:

Don't think you're getting what I'm talking about, when playing normally I do try to avoid violating the rules, but with this warning status in effect I have to play extra cautiosly, so it should be obvious that it would impact my game experience.

 

So you just have to play normally, as such it actually won't impact your game experience.

You're literally contradicting yourself.

  • Cool 1

Share this post


Link to post
Share on other sites
Players
127 posts
3,089 battles
1 minute ago, El2aZeR said:

 

I am well aware. Doesn't make it any less easy.

Also WG is allowed to read Windows logs now?

 

 

So you just have to play normally, as such it actually won't impact your game experience.

You're literally contradicting yourself.

I don't know about that, but the error monitoring program could get permissions to read specific logs.

Playing extra cautiosly, isn't playing normally - so how is that contradicting myself?

Share this post


Link to post
Share on other sites
[TORAZ]
Beta Tester
15,786 posts
26,801 battles
3 minutes ago, InfinityIncarnate said:

I don't know about that, but the error monitoring program could get permissions to read specific logs.

 

Because turning your game into a trojan horse surely is the way to go?

Besides, even with access to system logs faking a crash is still hilariously easy. Those even get logged as crashes so access to logs would do precisely NOTHING.

 

4 minutes ago, InfinityIncarnate said:

Playing extra cautiosly, isn't playing normally - so how is that contradicting myself?

 

If you normally do not incur penalties then there is no need to play "extra cautiously", as such any perceived difference is entirely in your head.

Share this post


Link to post
Share on other sites
[BAD-A]
Beta Tester
2,018 posts
13,254 battles

It happens. What does it matter? The worst that will happen is that you turn pink for a couple of games, something that you can get rid of in less time than it takes to create a thread and argue the toss about it.

 

We get so many of these threads and every one is pointless.

  • Cool 1

Share this post


Link to post
Share on other sites
Players
6,338 posts
14,260 battles
1 hour ago, InfinityIncarnate said:

But that wasn't me, I didn't put the team at a disadvantage, it's not my fault that the computer crashed, and because the game did not allow me to reconnect to the match when I got back into the game, then it was actually partially at fault to.
I usually don't have any issues of this sort, but thats besides the point - I didn't leave the match, my computer crashed, which I had no control over, so I don't think that it's is reasonable to punish with a warning.

 

How a pc is shutdown is logged, so if you manually shut it off/restart it, it will be reflected in the pc logs. And guess what, I'm sure that it could be made to be checked if the game wasn't shutdown by normal means, basically if the game client wasn't shutdown normally, it could be made to check those logs.

 

It may be that it's appealable, what I'm talking about that it shouldn't happen in the first place. In these cases, warnings and punishments, should only be issued when the rules are intentionally being violated, not when the computer or game client crashed.

I'm pretty sure that it's not totally impossible to add extra code to the game so it can tell truthful crashes apart from faul intent.

But why bother adding in hours of extra code for a little bit fewer pinkerstinkers in the game? Just spam a couple coop games or operations and you should be rid of it.

Share this post


Link to post
Share on other sites
Players
127 posts
3,089 battles
1 hour ago, El2aZeR said:

 

Because turning your game into a trojan horse surely is the way to go?

Besides, even with access to system logs faking a crash is still hilariously easy. Those even get logged as crashes so access to logs would do precisely NOTHING.

 

 

If you normally do not incur penalties then there is no need to play "extra cautiously", as such any perceived difference is entirely in your head.

What are you talking about, turning the game into a trojan horse? Having the error monitor being able read specific windows logs, won't turn the game into a trojan horse, further more, it's not like the game will be infecting any files just because of being able to read windows logs. Force closing I don't believe is logged as a crash, as for what other methods you're talking about in regards to making the game crash, I have yet to hear about.

There is a need to play extra cautiosly, when the warning status is effect, to make sure that not even accidents happen, that is what I mean with playing extra cautiosly - because while playing normally and playing by the rules, accidents may still happen.

  • Boring 1

Share this post


Link to post
Share on other sites
Players
127 posts
3,089 battles
Just now, NothingButTheRain said:

I'm pretty sure that it's not totally impossible to add extra code to the game so it can tell truthful crashes apart from faul intent.

But why bother adding in hours of extra code for a little bit fewer pinkerstinkers in the game? Just spam a couple coop games or operations and you should be rid of it.

Because, it's of inconvenience to players, and crashes could still happen while the warning status is in effect, which would escalate to more severe punishment.

Share this post


Link to post
Share on other sites
Players
6,338 posts
14,260 battles
Just now, InfinityIncarnate said:

Because, it's of inconvenience to players, and crashes could still happen while the warning status is in effect, which would escalate to more severe punishment.

Wanting to add code for every single instance of not having to add punishment anymore is kinda similar to wanting to add a car repair garage every 3km of every road in case some car breaks down near it.

 

Don't blame me, I'm merely conveying a message.

  • Cool 1

Share this post


Link to post
Share on other sites
[TORAZ]
Beta Tester
15,786 posts
26,801 battles
12 minutes ago, InfinityIncarnate said:

Force closing I don't believe is logged as a crash, as for what other methods you're talking about in regards to making the game crash, I have yet to hear about.

 

You have never heard about the reset button?

Or the power switch?

 

And I don't believe you know what a trojan actually is, don't you?

 

12 minutes ago, InfinityIncarnate said:

because while playing normally and playing by the rules, accidents may still happen.

 

The last time I accidentally got pink was well over a year ago.

So no, if you're not normally playing like a douche then it won't.

Share this post


Link to post
Share on other sites
[THESO]
Players
4,255 posts
33,590 battles

loltopic....

 

if u can't maintain integrity of ur hardware it's ur fault. on a sidenote: it not even has to be ur personal fault to be legit, simply because no matter how u try to screw it, with one booting out of match for whatever reason that team is in a disadvantage. and thus there are pneutral punishments for leaving battle, as there simply could be nothing else than simple measures in place. u leave battle early 'n alive u get punished. simple.

 

also, how in hell wg should rknow if someone botted out, cut the cable, melted his pc or woatever? from a technical viewpoint, plz explain how that should work lol?! :Smile_popcorn:

Share this post


Link to post
Share on other sites
Beta Tester
2,903 posts
22,225 battles
Vor 10 Stunden, InfinityIncarnate sagte:


Playing extra cautiosly, isn't playing normally - so how is that contradicting myself?

I was pink yesterday  (for good reason accidentally torping a teammate) and just played 2 games normally afterwards. Like a miracle the pink status was lifted off me because normally I don't damage teammates.

To me it sounds like you either worry about nothing or your regular game style is too ruthless. Seriously, you are getting fired up about a non-issue.

Share this post


Link to post
Share on other sites
[BAD-F]
Beta Tester
798 posts
16,110 battles

Do you always go pink when game crashes?

I am convinced that logging back into game while it is in progress does not give you pink.

When I think about it that should not be a case, to avoid abuse of system.

Last time I crashed it was in CB and I did not turn pink, does system work differently there?

Share this post


Link to post
Share on other sites
Players
506 posts

I had a lot of these in the past and it let 2 times to the failure of my motherboard so I had to replace it with a new laptop. But should I have to spend money just to fix the problem? Yes and no. If I do want to play I have to fix the problem(in my case spending money). If I don’t then I can just play another game. Thing is, the rest of the players should not be forced to have a bad game because of my computer. WG sees it also at a downside if one faulty PC ruins the game for an entire team. They don’t really care much about having a a player with a faulty pc and would rather see the player banned. Someone has to pay and it is you (and could have been me also)

Share this post


Link to post
Share on other sites
[NWP]
Players
2,062 posts
18,465 battles

@InfinityIncarnate

 

Dear Friend, I know how you feel. You did not abandon the game yet you are pink.

We all have experienced that. For one reason of the other we get out of a game, be it internet failure, power failure or a crash as you describe. And yes it is not your fault.

However, there is no way around it. You and all of us have to live with that. As I assume your comp doesn't fail every day it isn't so serious.

Further to this there is no way WG can know if you pulled the plug out or your motherboard exploded or your hard disk decided to go on holiday. 

So end of story.

 

Anyway, there is nothing you can do and it is not serious. Just do two battles in CoOp have a bit of fun or try a new ship and it will be over in 30 minutes.

 

Regards

Saltface

  • Cool 1

Share this post


Link to post
Share on other sites
Players
506 posts
27 minutes ago, Saltface said:

@InfinityIncarnate

 

Dear Friend, I know how you feel. You did not abandon the game yet you are pink.

We all have experienced that. For one reason of the other we get out of a game, be it internet failure, power failure or a crash as you describe. And yes it is not your fault.

However, there is no way around it. You and all of us have to live with that. As I assume your comp doesn't fail every day it isn't so serious.

Further to this there is no way WG can know if you pulled the plug out or your motherboard exploded or your hard disk decided to go on holiday. 

So end of story.

 

Anyway, there is nothing you can do and it is not serious. Just do two battles in CoOp have a bit of fun or try a new ship and it will be over in 30 minutes.

 

Regards

Saltface

He is afraid that one time it might happen several times within a short time frame and will lead to more serious consequences which is understandable. Identifying the problem if it occurs often is the solution to avoid some more serious punishment. I was in His situation due to a faulty PC and I also expected a potential ban.

Share this post


Link to post
Share on other sites
Players
127 posts
3,089 battles
49 minutes ago, kapnobathrac said:

He is afraid that one time it might happen several times within a short time frame and will lead to more serious consequences which is understandable. Identifying the problem if it occurs often is the solution to avoid some more serious punishment. I was in His situation due to a faulty PC and I also expected a potential ban.

That is exactly the issue, hence why I think they should at least make it so the client can tell the difference between quitting, force closing and actual crashes. Because as far as I'm aware, the warning status is given because other players have reported the inactivity.

Share this post


Link to post
Share on other sites
Sign in to follow this  

×