Horizons Combat Logging My Answer

[Muss]

With the exception of flying with my son, I have very little human interaction in ED, in fact I had my first actual conversation the other day and have been killed by a cmdr once.

Now onto the point, I have a new video card and have a number of crash's lately, so it is a simple fact that people can have their system crash.

What should happen to when you disconnect (crash,combat log, ISP down, dog ate your router, whatever)

For Your Attacker:
- Your ship should remain active and go on NPC autopilot.
- Your ship is now an NPC and the attacker is notified and can do as they see fit and collect their bounty reward ect.

For You:
- You do not get penalised (we cannot be sure why your discoed) but when you log back in, an NPC with the same equipment ect as your attacker will be on you in thirty seconds.
- You are warned of this before it happens.
- Your account should have a combat disconnect recorded against it.
- Regular "Combat disconnects" will limit you to solo play.
- Once a period has passed where your computer/you can/will stay connected during combat you will be notified that you can return to open play.


This will do the following:
STOP THE CHEESE AND WHINE threads

o7

 

[foebits]

Why is this even an issue? All this would do is make it even easier to heat cancer someone to death. If you don't want people combat logging then don't interdict them. Just as people who don't want to be player killed just need to simply not play in open.

 

[Gator Country]

If your computer is crashing that regularly after installing a new video card, I'd be looking into the cause of the crashing and trying to fix it.

 

[Pville_Piper]

If your computer is crashing that regularly after installing a new video card, I'd be looking into the cause of the crashing and trying to fix it.

I think the OP is using it as an example... Not too bad of an idea but it would punish those who legitmately have an issue as most NPCs are relatively easy to kill.
The solution is if you don’t want to PVP, stay out of open and join a group if you want to see people.

But yes, cutting the cheese and whine factor would be just about worth it...

 

[DragoonKnight]

Muss,
I dont think the changes you want are possible with a peer-to-peer network architecture.

The Combat Disconnects counter is a good idea IMO and can be implemented (start with a value of -1 for all players; increment counter by+1 when you login; decrement when you logout through the main menu - if you logout any other way then the counter is not decremented). Would be even better if other players could see that number when they target you. Too many combat logs in one month would get you locked out of open.

 

[Alex Brentnall]

As above it'd be nice but your own pc sends your ship position, damage data, etc to the other players. You disco and no data is sent so persistant ships post disco isnt a thing. Fd have commented on this and im sure have implemented a system similar or more sophisticated than above.
They do have banwaves for cheating and have said they will be clamping down on c-logging.

Currently the red whine comes a lot from that the 15 sec timer isnt classed as c-logging but to the attacker looks the same.

 

[Solid Snake]

Why is this even an issue? All this would do is make it even easier to heat cancer someone to death. If you don't want people combat logging then don't interdict them. Just as people who don't want to be player killed just need to simply not play in open.

Better yet if someone is just gonna log every time they get interdicted by a player they should just play in solo. Player interdiction is a part of open play so why would the solution be to just not interdict them if you don't want them to log?

 

[foebits]

Better yet if someone is just gonna log every time they get interdicted by a player they should just play in solo. Player interdiction is a part of open play so why would the solution be to just not interdict them if you don't want them to log?

ded in what I said Mr.Snake.
That was pretty much inclu

 

[Muss]

But they don't and this affects the play of people who do

- - - - - Additional Content Posted / Auto Merge - - - - -

If your computer is crashing that regularly after installing a new video card, I'd be looking into the cause of the crashing and trying to fix it.

Had lots of driver issues now resolved.

- - - - - Additional Content Posted / Auto Merge - - - - -

Muss,
I dont think the changes you want are possible with a peer-to-peer network architecture.

The Combat Disconnects counter is a good idea IMO and can be implemented (start with a value of -1 for all players; increment counter by+1 when you login; decrement when you logout through the main menu - if you logout any other way then the counter is not decremented). Would be even better if other players could see that number when they target you. Too many combat logs in one month would get you locked out of open.

the server cant always know why you discoed
- Pull you cable
- use a key or joystick switch to trigger a batch that runs psexec to kill your ed process
- someone at your isp tripped over a cable
- your mrs is sick of your 10 hour ed sessions and pulled your power cable
- you video card crashed

my idea is that if you choose to disco during combat OR if you disco in combat cause your mrs hates you playing ect ect ect then the player that has spent time finding you should not be punished, (assuming it was your wife dog isp) you should not be punished so thats why your attacker gets to keep fighting the NPC version of you and when you log back in you have to fight the NPC version of him or her.

and if it keeps happening ED should not allow you to affect other peoples game play like this, so until the issue is resolved (or you choose to stop being a cheat) you should be restricted to solo.

- - - - - Additional Content Posted / Auto Merge - - - - -

Better yet if someone is just gonna log every time they get interdicted by a player they should just play in solo. Player interdiction is a part of open play so why would the solution be to just not interdict them if you don't want them to log?

as i said above they don't and won't

so make them

 

[Othniel]

I say leave it the way it is. I have had my share of run-ins, but none took the cake like an Op shooting two torps that took down my 2250MJ shields and left 60% hull- I was toast, but it just seemed too easy for him to destroy me, even though I had a well modded ship- I looked it up, bought torps, and when to Juri to get them modded... added the same special effect, and I couldn't even bring down shields to 50% on an expert NPC Python's shield with one.. so I would like to say who is keeping people from cheating?