Nothing was being saved, and the tutorial needed three units

Take the client from the download page again. This build is r0025 and the server refuses every build before it, so whatever you have installed now will be turned away. Three builds went out since the last notice here without one of their own, which is the first thing to put right.

The two notices before this each said the tutorial was fixed. Neither was the end of it, and the reason is worth stating plainly rather than quietly shipping a third attempt.

The first real cause was not the tutorial at all. Every handler on this server read who you were from an HTTP session, the kind a browser carries in a cookie. The client cannot carry one: it drives all of its traffic through cocos2d-x's HTTP layer, which never switches libcurl's cookie engine on, so no cookie was ever sent. Every request from a real phone arrived as a brand-new empty session. Each write checked whether it knew who was asking, found that it did not, and skipped. Nothing was stored. Not your summoner, not tutorial progress, and equally not decks, items, friends, guilds, arena, campaign, raids or presents. The loop was only the most visible face of it: the client asked what it had cleared, was told nothing, and replayed the opening forever. Identity is taken from the request itself now, before any handler runs, which repairs all hundred-and-thirty-odd of those places at once.

That should have been caught here and was not. Every test this server had used a cookie jar, which is exactly the capability the real client lacks, so twenty-six passing tests sat happily alongside a phone that could not get past the opening. There is a test now that is deliberately cookie-blind and identifies itself the way the client actually does.

The second cause is this build, and it is smaller and stranger. With saving repaired a device gets through avatar creation and into the world, but the Home screen kept prompting for the summoner button and walking players back into creation. The client clamps the tutorial chapter at 12, so 12 is the end and no higher number escapes it. Chapter 12's exit asks one question: does the active party hold exactly three members. A new account here was seeded with one unit, so the answer was never yes and the step fired again every time. It tests for equality rather than for three or more, which is why one unit was as stuck as none would have been.

New accounts start with three now. The leader is the same as before, joined by two of the game's own three-star elemental starters taken from its unit table, so no unit is invented and each has real stats.

If you already have a save it repairs itself. An account made before this build owns a single unit and cannot escape the prompt by playing, so the server grants the missing starters the next time it sees you. There is one deliberate exception: if you have already arranged your own party then that team is yours, and you will not be handed units for choosing a small squad.

One more thing that had been reported and looked ignored. The Facebook wording people kept seeing does not live in the app, which is why patching the app changed nothing on screen. It lives in a text dictionary the client streams from this server, and that still held every retail Facebook line, the connect dialog included. It is rebranded now. A related fault had been keeping even corrected art from arriving: the client asks whether a cached file has changed, this server never answered with a date, so the cache was never refreshed and only clearing app data got through. It sends a real date now and answers properly when nothing has changed.

This release's fix is entirely on the server. The new client exists so that the version gate matches and for no other reason, so if the prompt still returns after you install it, the app is not the suspect and that is worth reporting with the device model and the Android version.

Nothing here carries over. The world is cleared before it opens properly.