And I am pretty sure you can't see yourself with these multiple clients![]()
And I am pretty sure you can't see yourself with these multiple clients![]()
I have no argument here. And I am also fairly sure they will block it eventually and take the unfair profits from the offenders as they did with the founders world exploit (or not, but I don't care). Bounty farming would not be an issue everybody is whining about, so my fix to the whining issue should workMy point being : it's pointless trying to bounty farm yourself when it's a lot easier to put yourself in to 2 stations on a trade route and trade without moving to make money.
I have no argument here. And I am also fairly sure they will block it eventually and take the unfair profits from the offenders as they did with the founders world exploit (or not, but I don't care). Bounty farming would not be an issue everybody is whining about, so my fix to the whining issue should workAnd it is also dirt cheap to implement and wont' take any additional server resources.
Nothing can stop the all mighty "End Process" button besides your ship being left in-game, which may not even be possible with this game engine
P2P Networking at it's finest.
The combat logging is only relevant when you are in the same instance (as in you just interdicted somebody or got interdicted). If you managed to jump away, I think you can just drop from SC and immediately switch to Solo, all within the game mechanics. You won't be in danger right after SC exit and should be able to log out without the 15 sec timer.Bounty farming isn't the issue it's when you've chased a player through 5 star systems for a 50 mil bounty and when their shields go down they pull the plug lol
The combat logging is only relevant when you are in the same instance (as in you just interdicted somebody or got interdicted). If you managed to jump away, I think you can just drop from SC and immediately switch to Solo, all within the game mechanics. You won't be in danger right after SC exit and should be able to log out without the 15 sec timer.
You probably see the pattern here: game is designed so that you can hide away from an attacker if you choose so. That means we don't have combat logging issue, but rather a whining issue. And my fix for the whining issue will fix it easilyYeah but most don't, they'd rather bail at the last minute when things go wrong. Logging out with the timer is fine even if it is a bit short.
I think FD knows about it. I would believe they are trying to find a workaround. There will be a lot of complications.
How about trying your own workaround - create a pvp group. Invite all your trusted non combat logging friends.
-invite other players who like pvp.
-boot anyone that repeatedly combat logs. Have a 3 strike rule.
Bobs your uncle.
Will keep you occupied untill FD finds a solution.
Easy solution: If someone pulls a logoffski (their P2P and connection to game server severed), their ship remains in play and immobile for 60 seconds. Whatever happens is transferred to their save.
No, it's entirely possible to do. All it takes is, spawning an enemy ship with the exact loadout and specs, into that instance. It probably wouldn't be completely instantaneous, since you would need to verify that it's a lost connection rather than a hiccup. Game saves aren't 100% client side, so it's likely the servers do actually store ship information. If it doesn't, well it possible to see someones loadout, so your game knows other players loadouts. why can't it just save the loadout of every ship in your instance? Once it has been determined that someone has lost connection, an npc avatar could immediately spawn to replace him. Npcs are already shared across multiple clients, so it should work for wings as well. So yes, it's possible in theory.How are you going to do that? It's a P2P game, there's only one server and it just adjudicates. If I disconnect my game by whatever means, there's no way you can keep my ship in the game for any length of time, because it only exists on my computer NOT the central server.
That's the reason it's NOT easy, and why they haven't fix it yet.
Spawning an NPC will certainly work here and your client already knows the loadout and everything just because you are connected. So, basically, if your instance is split because of a network issue, both parties will get an NPC to fight with. The only thing you need to do is to keep it displayed as an empty box so that the people asking to "leave your ship for 60 seconds" won't notice the differenceNpcs are already shared across multiple clients, so it should work in wings as well.
I don't necessarily support the idea, i think there are a few other, better ideas, but that's not a bad way to go.
No, it's entirely possible to do. All it takes is, spawning an enemy ship with the exact loadout and specs, into that instance. It probably wouldn't be completely instantaneous, since you would need to verify that it's a lost connection rather than a hiccup. Game saves aren't 100% client side, so it's likely the servers do actually store ship information. If it doesn't, well it possible to see someones loadout, so your game knows other players loadouts. why can't it just save the loadout of every ship in your instance? Once it has been determined that someone has lost connection, an npc avatar could immediately spawn to replace him. Npcs are already shared across multiple clients, so it should work for wings as well. So yes, it's possible in theory.
I don't 100% support the idea, i think there are a few other, better ideas, but that's not a bad way to go.
OK a couple of issues.
First up, how do you determine that it was intentional and not a flaky internet connection?
Secondly, ok suppose you've got some way to do that and you've actually spawned an identical NPC... then what? You're giving them a free target to take the last few pot shots at? Or is it gonna fight back? If it's going to fight back, at what skill level do you set it? From the other pilot's point of view, he's gotten his enemy down say 15% hull and suddenly he disappears. Oh, poop! Then he reappears, hah what!? Then he either sits still and appears to give up so he can be shot, or he spins on his tail and starts fighting like a demon (both would be comparisons to the real pilot's flying skills if they're not matched).
Third, OK so suppose you can find out for sure that the pilot intended to disconnect, AND you can roughly match his piloting skills, what then? Apply a fine or bounty for logging out? Ban him from open (because there's not enough people leaving open already)? What happens if he argues and says his cat pulled the power plug, or there was a storm and the power went out? Are FD going to have the cat put to sleep, or research weather patterns & lightning at the time in the pilot's location? Or just give him the benefit of the doubt? What about if there's a pattern of logouts, you ask? What about if I am playing from a place with really dodgy internet connections and power supplies like pretty much anywhere in South East Asia where daily outages in both are a normal thing?
It's not ONLY for technical reasons that it's pretty much impossible - there's plain old human, circumstantial reasons for it too.
OK a couple of issues.
First up, how do you determine that it was intentional and not a flaky internet connection?
Secondly, ok suppose you've got some way to do that and you've actually spawned an identical NPC... then what? You're giving them a free target to take the last few pot shots at? Or is it gonna fight back? If it's going to fight back, at what skill level do you set it? From the other pilot's point of view, he's gotten his enemy down say 15% hull and suddenly he disappears. Oh, poop! Then he reappears, hah what!? Then he either sits still and appears to give up so he can be shot, or he spins on his tail and starts fighting like a demon (both would be comparisons to the real pilot's flying skills if they're not matched).
Third, OK so suppose you can find out for sure that the pilot intended to disconnect, AND you can roughly match his piloting skills, what then? Apply a fine or bounty for logging out? Ban him from open (because there's not enough people leaving open already)? What happens if he argues and says his cat pulled the power plug, or there was a storm and the power went out? Are FD going to have the cat put to sleep, or research weather patterns & lightning at the time in the pilot's location? Or just give him the benefit of the doubt? What about if there's a pattern of logouts, you ask? What about if I am playing from a place with really dodgy internet connections and power supplies like pretty much anywhere in South East Asia where daily outages in both are a normal thing?
It's not ONLY for technical reasons that it's pretty much impossible - there's plain old human, circumstantial reasons for it too.