I’m not sure. I really don’t know much about achievements since I don’t pay attention to them when playing, and they didn’t exist when I started coding. Actually I don’t think I’ve played much with achievements, since I generally play stuff before they’re implemented.
There’s a *check_achievements command, but it’s not a reliable method.
But there’s a big caveat. Part of the reason there isn’t more public documentation about ChoiceScript achievements is that there isn’t a very reliable way of making sure that they stick around. On iOS and Steam, Apple and Valve provide official mechanisms for registering achievements that stay achieved. On Android and Chrome Web Store, the user installs the app, so as long as the app remains installed, the achievement stays unlocked. But on the web, it’s very easy to lose your achievements (e.g. if you clear cookies and local storage).
If we host the game on choiceofgames.com , we can try to take care of this for you, but not just anybody can put a game up on their website and have reliable working achievements.
At some point, I’d like to set up some code and instructions allowing players to register their games with Google Play Game Services, in which case Google will store your players’ achievements (but they’d still have to login first).
For now, it’s not totally possible/reliable to create a truly “permanent” boolean.
1 Like
