The idea of the minimum username length is that users should have at least a meaningful syllable.
This requirement was introduced 7 years ago for the registration, so affecting new users. However, 100k+ accounts already existed back then.
We have 162 semi-active accounts with less than 3 characters, so this game change should be rolled back @Jip
There is no solution.
We don't know the cause. It could be a different individual problem on each pc. It could be something general with some network settings. It could be a bug in our software. There are multiple problems we noticed, but none of them explain the disconnect issue.
There is a slow progressing attempt to rewrite the ice adapter too be able to diagnose the problems better. But there's no ETA whenever I have time and motivation to progress there.
For some reason the new game patches have resulted in the commander and mobile artillery units exhibiting adverse gameplay.
For example you'll target an artillery piece with the commander that just came into view and the commander will wildly run away.
the exact opposite of the expected behavior.
this is made even crazier by the fact that there are no rocks or anything in between,
it's the same sort of bad pathfinding as you'd get in vanilla FA when you'd create a formation from a bunch of scattered unit and instead of forming the formation at the closest point to the command they'd all move back to your base first and form the formation there and then move forward.
Except here there's no indication that the com would ever stop.
I've been experiencing this bug with a number of units in ladder gameplay.
the attack command for artillery pieces has become functionally useless when targeting any unit (targeting still works on buildings) but when targeting a unit the artillery unit will for some reason start to pathfind erratically instead.
more often then not "running away" from the intended target making the command fail.
This is really ruining gameplay something went amiss and this must not have been picked up on in testing.
in the replay the attack command doesn't show up (I'm holding shift) but I did issue one and as you can see it's empty space between the arty and my com but the com immediately starts running down towards my base rather than towards him. (my com was within view range but not yet shooting range and the movement prevented my com from shooting at it any further)
this behavior is infuriating while playing...
#22252375
I went back into the replay and looked at it from my point of view.
And it's unmistakable. I was moving up and the instant I issue the attack command the commander's legs spin and he heads down whereas the arty is above, in view range and targeted :
you can see a second later i'm already much further down and attempting to head back up using a move command instead since that's the only remaining option to kill that artillery unit with my com as attack command has failed me.
If I get better examples I'll post.
Why do I even need "yet another button" to enqueue? Why not automatically be enqueued as soon as you check any of the queues.
@mostlostnoob sorry, that's a missreading of what's written.
the operative "it" in the context of this thread was the FAF crash.
I said "running it from steam". which implies it did run.
@thecore I think it should then be "Forged Alliance Forever" and "Offline Forged Alliance Forever", then.
@mostlostnoob .exe
read the title of this thread. I'm on linux. I can only use the tools FAF provides. plus I have no issues whatsoever under steam.
@thecore you have "Downlord's FAF client" that should just be called "Forged Alliance Forever", as per the website that we're currently on that's what it's called and what you get when you download FAF.
then later you have "Forged Alliance Forever" which I assume is the python FAF. it's a bit misleading and confusing to have both and label them the way you did.
this time running FA from steam does not fix it.
and the log file didn't generate. for this second crash
@thecore FAF and python FAF seem to be mislabeled in this list...
