I’m back, yes really. Here’s a suggestion, hear me out.
Currently when you join a server with sv_enforceGameBuild set to 2189 or whatever it will close your game without any prompts, and then start back up quickly. I would like to see some prompt like “Your game needs to restart in order to play on this server as it’s running a different game build.”, maybe also some “dont show again” tickbox with it.
While this is understandable - is this not already basically done by the launch splash saying “Transitioning to another build…” or such?
What are users exactly getting confused about? Maybe there’s a better solution possible as well.
Well I mean show a prompt before quitting the game in the first place so people know what’s going on. Trust me I know a lot of idiots joining servers with that claiming their game “broke” or whatever. I’ve heared endless people say that. Including people in my community which is why we still don’t use the new DLC and instead stream the cayo map 
I think the problem is that some players (not all) just don’t know what ‘transitioning to another build’ actually means. It’s too, er, technical for some. They assume something has gone wrong, and quit the op, and go looking for another server (or end up breaking their local FiveM install possibly, but I don’t know that for a fact).
I think it just needs the language to be really simple for non-technical people to understand, in words that tell them what to expect: i.e. this FiveM client will close because the latest development-version is required, a new one will install, and that they should just wait patiently, etc.
We just tested this again…
1 - the old FiveM (release) client gives no warning at all of what is coming - it just quits to blackscreen. This, in itself, spooks some of the players (if they have short attention, impatience, etc).
2 - the (presumably minimised) FiveM (release) client then goes into a Game Cache rebuild which takes a little while. Not too long, but again maybe long enough for some folks to get edgy if they don’t know what to expect (god help them if they pull the plug though!)
3 - after that, the old FiveM client says “transitioning to a new build” (which in itself is perhaps a little unclear for the non-tech folk), and then goes dark again. There is a moderate wait, and then the new (Canary) build appears, and (wonderfully) will hook straight in to the correct server.
The mechanism is great. Works well. It’s just that the signalling of it, before it starts, is absent/unclear and some folks just don’t have the patience or the awareness to realise what is actually happening. Most of the ones we’ve had comments from don’t even know what the Canary build is, or what it means to them.
I think this is just a case of better ‘pre-warning’ at the very first moment when entering a server running canary - before Fivem (release) even goes dark and starts updating the game-cache. Urge patience, and tell them it will all work, and probably they’ll sit on their hands and wait a bit longer.
Does that make sense? Hope so.
Look bubble guy or whatever your name is basicly this is a UX question / improvement. I’ve heared from endless people that they get really confused the first time their game shuts down, because they’ve never seen it before in fivem. Which is also why we’re not currently using it on our server.
Also why isn’t 2189 the default game build enforced? Is it because of the map incompatibilities?
Yeah something along the lines of:
“This server requires you to run the lastest build, we will automatically switch the version for you. This might take a minute and FiveM will close and relaunch and automatically connect you to the server. Please be patient”
Would be an great addition. Maybe even a “press okay to continue” allthough that might be overkill.
JFYI, Canary is a separate thing from cross-build game compatibility.
Some features are still missing/not ported, nobody has done the 3-day process of running Diaphora to convert debug information, and some older resources (and ‘clothing addons’ made using some weird workaround) may be incompatible.
I see a few more things mentioned here, anyway, which would lead to the following flow, maybe:
Fabulous - really - spot on. Totally reasonable suggestions @nta - thanks for hearing us out. These would be really helpful improvements if you’re up for adding them. Thanks!
And my apologies re the Canary client build thing - I’m sort of learning some of the nuances as I get deeper in this side of things.
Seems like a very good flow.
My phrasing was of course just example, whatever works and is easily translatable.
I think the idea of having a cancellable dialogue with a timer is great.
BIG thumbs up from me
First phase of these changes is available in latest client experimental branch, only the build remembering is missing currently.
This includes download prompts for build switching being in-game as well:
Hello,
It’s nice 
I noticed 3 things :
Ah, right. Perhaps should indeed move to clearTimeout instead of an odd flag.
Likely a bug in angular-l10n module, not sure if easy to fix. 
→ seemingly happens if you use L10nMissingTranslationHandler instead of L10nTranslationFallback which got added in a later version. Fix pending!
Unrelated bug indeed. Likely happens as connection is initiated before UI finishes loading.
yäääääääääääy good job mate! thanks for the quick implementation. i never thought this day would come
Hi @nta
Just thought it appropriate to follow-up on this and let you know that the changes you made are working extremely well for us, and we’ve had very few problems since we swapped to using the enforced-build client. Sure, one or two players get warnings about GTA caches that they don’t understand straight away, but we’re coping with those, providing support and they’re usually getting in-server pretty quickly once we’ve hand-held them a bit (usually it’s client-side setup issues anyway, tbh).
As far as our worries regarding players disconnecting between client-restarts, that has now completely gone away, and everyone seems to be making the jump smoothly.
Yeah, I know it’s odd to post up a reply that doesn’t raise a huge bug or REEE for Moar Stuff™, but I know what it’s like to be in your shoes… so I thought a “thanks, you’ve done a great thing” post might be a nice change for once.
Really appreciate what you did for us there. Thanks heaps. Small change, big impact. My favourite type! 
