Which is fine. The central idea of this thread is that we are all informed you have decided to quit prior to that happening.
What is your position on that idea?
Make menu logging visible in game
- Thread starter Ouberos
- Start date
Which is fine. The central idea of this thread is that we are all informed you have decided to quit prior to that happening.
What is your position on that idea?
I'm fine with that. I was just reacting to the thing about the UPS delivery.
Lestat
Banned
Well, Ouberos I am looking at the issue from a player that hardly had the best connection. Due to Rural areas I live in. I remember people complaining about my connection. It was crap. But as a Tech I can see the issue of players using it as an Exploit to ruin other players gameplay.
Knowing that the other party, IS menu logging, which is basically the same as running Justifies an honest pirate, to shoot to kill. Pulling the plug, is a whole different matter and subject. Again: I have stated, all of this, could be recorded by the attacker. Basically, it offers two things. Proof of disconnects and how they happened. Plug or menu. Yes we all lose connections, myself included; especially in open play.
I swear, if I don't get off at least half as good as Ouberos in your next book, I'm gonna gank some noobs in Colonia
Ouberos is a consummate professional in his craft:
I'm flatteted. But of course Matt only wrote about the best bits.
Or are they the best bits because Matt wrote about them?
Either way you should all read it.
Why don't you go.
Because it's like, my idea?
This is a thread in the Suggestion sub forum. People come here with Suggestions for developments which can go in the game. Then other people pick holes in them or ignore them. So far this thread has been a positive experience. Lots of people agree this would be a good idea.
Random shouting about modes belongs in the modes sub forum. Go there and do it. It is not relevant to this thread.
Unless you have an opinion on the original idea? Feel free to form one. I think opinions are so important.
Try to use normal sized words. It's more grown up.
He seems to be targeting players like me. Who can't afford to pay to Play in the open or solo players. But I do read all the topic.
Great, then we can blame them
The difference between these two things is that jumping one's ship to another system is a CMDR action performed via in-game equipment in a wholly in-setting context, but menu logging is a player action performed via their game client.
I don't feel the game needs to announce player actions in an in-character context. This would set a negative precedent that may make it more difficult to implement better mechanisms in the future...not that I really expect better mechanisms to come, but an extra fifteen seconds of wasted time every other encounter is a small price to pay for not closing that door, IMO.
It's as well within the bounds of the game as the other activities you mention.
The only issue is that the game provides a way to spontaneously opt-out of content (essentially any form of danger that can take longer than 15 seconds to resolve) that one has already opted into.
The game has been able to relay clients that could not directly connect before. Even used to be a setting to force it in AppConfig.xml...not entirely sure if it still works or not.
Rubberbanding can certainly occur when the connection or client load gets really bad, but latency in and of itself won't cause a shot that appears to hit to miss because the latency compensation scheme used each client's own perspective takes precedence when inflicting damage, even if the result looks absurd (a high ping can mean two CMDRs in a duel can each be shooting the other up the tailpipe from their own perspectives, because the game says both perspectives are correct).
If ping is high enough to be a major issue through latency compensation, then matchmaking should simply refuse to pair such clients with each other.
That would be ideal. I don't think it happens though; I've been in an instance with two other players - I could see both of them and they could both see me, but they couldn't see each other. Under most CL suggestions we see, I think their game clients would both replace the other with an NPC! I would then possibly see both of the players and both of their simulacra in my instance. How the respective clients would finally report outcomes to the server is anyone's guess. Basically, suggestions for dealing with clogging need to take the nature of P2P into account, or they are useless.
Yes.
This suggestion would also protect people that log out via the menu (allowed under the TOS) from accusations of deliberately disconnecting their router or task-killing (not allowed under the TOS) by explicitly showing the other party, who may be recording the incident, that it is the former.
And I and many other don't care how YOU want to play the game, so if they want to log out and deny you a kill tough. The only types FD need to ban are seal clubbers.
Missing the difference between a menu log and a hard disconnect/task-kill is understandable in the heat of the moment, but if there is video of it, it's almost always possible to tell the two apart in hindsight.
Craith
Volunteer Moderator
Could be a 'contact lost' for menu logging and 'contact signal distorted' for anything related to connection loss (which could be a combat log, or something else)
Deleted member 110222
D
I agree. A notification will mean I will know when to stop extracting cargo and just instead make sure my customer logs back in only to find a menu, not a cockpit.