ALXS was the final version of a lot of asynchronous multiplayer game attempts that ended up failing terribly one after another.
The first iterations were a card trading game, and the latter was an incremental 'Idle' game.
The initial game design of ALXS was done before any form of thought was put into it, I thought "Wouldn't X be cool?" Without thinking whether X was absolutely necessary.
Approaching this project was quite an incredible feat. I had never made a proper full game before, let alone touched Multiplayer...
The initial design went well, but as you'll soon read in the development section, the scope of the attempts tended to be SO big, they all crumbled under their own weight & tech depth, so nothing could end up being playested.
Except for, the title of the project: 'ALXS'
But by cutting down on the scope so much, nothing fun remained.
ALXS taught me all about the ins and outs of LiveOps. Running a game and doing maintenance, publishing backend changes and even cloud code!
The approach I took towards creating 'ALXS' was simple: Learn as I go. (This is a very dumb approach for this project). And that is exactly what I did!
While the games kept crumbling under mounts of tech debt, A lot of important concepts were taught to me here: Authentication flow, Dependency Injection (C#), JSON/Configs & Game economies
Some people called this game worthless, or not a real 'game'. Little did they know that most of this project was trying to understand how these Big live-service games worked.
Art was not a priority during this project.
As stated before, this project was much too big for what I can realistically produce. But! It was a great exercise to learn about the ins-and outs of All things Live-Ops!
Questions, offers or something you wish to tell me? Go ahead!