You are right - we should have used it, but tbh i've just completely forgotten about it.
ah hm yes, indeed if you go online it'll be 'fixed'. The stats that were generated during the downtime (going offline is a stat as well) have been lost unfortunately.
But i'll have look at fixing it on my end.
Our switch died which led to instable connectivity all day (it wasn't optimal for a few weeks now actually). Tonight after a reset it didn't work at all anymore.
I've installed a temporary switch now, and everything should be back to normal. There will be some planned downtime further down the road to replace the loaner with a permanent one.
Actually, i think you can, if you use the correct bytes.
Those arrows are present in the LFS font.
The url encoded LFS string for those arrows is :
It's url encoded because otherwise a lot of characters would be messed up in utf8 conversion (the forum uses utf8).
So decode that and you'll get the literal LFS string that you could try in your insim app.
Or try one arrow .. I think that's %5EJ%81%A9 for the first one.
You can already see it selects the japanese codepage (%5EJ = ^J) and then there are two bytes for the character (0x81 0xA9).
I can log client messages and commands if needed. One would just need to request logging and tell me the host name as I'll not be logging everything (I'm not an intelligence agency, 'ey).
I do log all client connections and that helped Fel's issue.
I'm guessing that LFS started but then returns an error relating to not being able to find files it needs anb then waits until you press a key. But you may not see that message if DCon.exe is hidden. It could explain why you see it in your list of processes, but cannot join it.
This error could be caused by LFS not knowing its working directory when it's started via alternate means. Check if you can explicitely set the working directly to the LFS path, in the startup command.
You could double check by reading the LFS log files. If there's nothing at all, it's surely a wrong working directory. Otherwise you may see the error listed in the logs.