I don't know if this is configurable -- Maybe too specifc to the server to be something that FTB-Launcher can deal with....
So, in the Launcher (the client) There is this message from the FTB/Launcher that begins "Forge Mod Loader could not connect to this server.. The mods and versions listed below could not be found .... "
I think that's the message generated on the client (the launcher). But what I'd like to be able to do is figure out if there's a way for the server to provide more data like
"Psst. download version X and you should be good".
It seems like this should be doable, but I doubt there's a mechanism in FTB-Launcher to query for such data WHEN the client cannot connect.
Anyone (?) think of a way through this to give the user just a bit more hint on what to do next when they fail to connect (user error, yes.. but it can save time and resources if the server can spit out a failed-msg that resides on the server when FTB/Launcher cannot connect.)
For example, in the server-properties, something that the FTB-Launcher can actually read/access to explain generically why a failed login occurred. Sure, not every attempt login that fails will be explained, but I'm betting a lot of my server's failed logins are due to version X != Y and thus a simple message "Try again and use _mod pack_ version Y so ALL your mods are up to snuff".
ps. the spell checker on this editor is full of eels.
So, in the Launcher (the client) There is this message from the FTB/Launcher that begins "Forge Mod Loader could not connect to this server.. The mods and versions listed below could not be found .... "
I think that's the message generated on the client (the launcher). But what I'd like to be able to do is figure out if there's a way for the server to provide more data like
"Psst. download version X and you should be good".
It seems like this should be doable, but I doubt there's a mechanism in FTB-Launcher to query for such data WHEN the client cannot connect.
Anyone (?) think of a way through this to give the user just a bit more hint on what to do next when they fail to connect (user error, yes.. but it can save time and resources if the server can spit out a failed-msg that resides on the server when FTB/Launcher cannot connect.)
For example, in the server-properties, something that the FTB-Launcher can actually read/access to explain generically why a failed login occurred. Sure, not every attempt login that fails will be explained, but I'm betting a lot of my server's failed logins are due to version X != Y and thus a simple message "Try again and use _mod pack_ version Y so ALL your mods are up to snuff".
ps. the spell checker on this editor is full of eels.