Remove stupid error code names.

Well I suppse they could post something like "TLS Handshake Failed" but would that be any better? Essentially the error codes are for FDEV use and giving us a longer detailed explanation would really achieve nothing except sending a lot of people hunting the internet to try and fix a problem theyt don't understand and probably can't do anything about anyway.
 
The messages are more to be useful to them than for us. It pinpoints the area of failure, probably also gives them some protection against the "experts" that are 100% sure what the problem is instead of listening to the solution or describing a line of goods that isn't even related to the issue at hand.
 
The messages are more to be useful to them than for us. It pinpoints the area of failure, probably also gives them some protection against the "experts" that are 100% sure what the problem is instead of listening to the solution or describing a line of goods that isn't even related to the issue at hand.
This one. There's multiple reasons which could result in an instancing timeout... but working out which specific instancing timeout occurred would be problematic. Codifying the same error against different places it occurs is a smarter way of reporting the error.
 
If there's a problem with the client side connection, just say so. If it's an instancing problem, tell us.

what is "mauve adder"? How many drugs had been passed around when they decided that was a good idea? 😉

Agreed. If it can provide a clear text message it can provide one that is useful to both client and service provider, the problem may be at my end.
 
so what would the message be?

Since it is very unlikely you will get an error message that specifically tells you what the actual problem is, especially when it comes to this sort of networking...

so would it really be that much better if you where told, "something went wrong when trying to instace"? Or "unknown server communication error", etc, etc, as that is what would the be the most likely replacements....

you would not see "your local firewall is blocking traffic and thus we cannot create a new instance".... as that level of details is not known.
 
How about something like this:

guru_meditation_error_animated.gif
 
Last edited:
The error code corresponds to an internal (alpha-) numeric code, but is a lot easier to remember (for support, google, etc.)
 
Yes, the error codes are for frontier, but still, a "connection error" message is lot more understandable for even a player, than "mauve adder"... Totally agree with OP!
 
OK... again: The idea is that the user is provided with a memorable and unique(!) to ED code that they can easily google or - galaxybrain.jpg - go straight to the knowledge base to retrieve this information:
Mauve AdderThis error appears when you experience a problem connecting to the matchmaking server.
  • If this error only appears when in-game with other players, it's likely port forwarding will help, we have a guide that shows how to set this up here.
  • Otherwise, log in to your router and look for any content filters and disable them, if available, try another router.

Sadly this is giving way too much credit to most players who instead write stupid posts all over the place which makes the google approach less feasible. 🤷‍♂️
 
OK... again: The idea is that the user is provided with a memorable and unique(!) to ED code that they can easily google or - galaxybrain.jpg - go straight to the knowledge base to retrieve this information:
Mauve AdderThis error appears when you experience a problem connecting to the matchmaking server.
  • If this error only appears when in-game with other players, it's likely port forwarding will help, we have a guide that shows how to set this up here.
  • Otherwise, log in to your router and look for any content filters and disable them, if available, try another router.
Sadly this is giving way too much credit to most players who instead write stupid posts all over the place which makes the google approach less feasible. 🤷‍♂️

...and the proposal is to improve on that.
 
The messages are more to be useful to them than for us. It pinpoints the area of failure, probably also gives them some protection against the "experts" that are 100% sure what the problem is instead of listening to the solution or describing a line of goods that isn't even related to the issue at hand.
Exactly correct. It's an old dev tactic 👍
I do it.
 
If there's a problem with the client side connection, just say so. If it's an instancing problem, tell us.

what is "mauve adder"? How many drugs had been passed around when they decided that was a good idea? 😉
Probably none. If people dont know whats happening, its easier to rubbish them and control their reactions and behaviour.

Seriously? rubbish didnt pass the filter? What century do you guys live in? What fairy tale kingdom do you hail from?
 
Back
Top Bottom