Tides of Revival, or Tides for short, is, put as succinctly as possible, a Massive ImSim. Well, it isn't that yet. But that's the ambition.

Here are some bullet points to describe the game:

• Single-player RPG set in a huge fantasy world played from an FPS perspective.
• The world suffers millenia-long cycles, consisting of two so-called "tides": Chaos and Prosperity. You are starting the game just as the Chaos tide is winding down - people are beaten, the world is unknown, monsters are out there, but the chance to kickstart the way to Prosperity is now!
• "Offline" generated, prebaked world. Created once on our dev machines and then shipped as part of the game, just as though you'd downloaded a big AAA RPG.
  • This will allow us to create a world that is larger and more detailed and interconnected than any AAA studio could feasibly make.
  • You will play the same game, the same world, as everyone else, hopefully allowing for a community to spring up and find cool locations or ways to play the game.
• A focus on immersion and believability. We try to stay away from game design "plot holes", and known truths, and instead think through the game from first principles. We're willing to bet that players are ready for and desiring NPCs that are smart: beyond trivial state machines and "must've been the wind".
• Dynamic dialogue and a world that changes with and without you.

For a more indepth discussion: https://www.youtube.com/watch?v=yoJ7ayDuaJQ

To get Tides to what we want it to be, we work on it in terms of releases, called Hills. A hill is not just an improvement in terms of features and amount of content, as though we simply continued to churn on the game along some vector towards a goal in the far distance. It is also an opportunity for us to choose a specific, temporary direction, and a promise that we will create something solidified and game-like.

Towards the end of each hill we will allow ourself the time, energy, and fun, to polish it up into something that is a playable whole, even if it means some of it will get torn down again as we start working towards the next hill. One hill at a time! (But with some foresight).

On a technical level, we will also allow ourselves a bit of engineering slack and to build up some tech debt, when implementing new experimental, exploratory systems and features. By adding hacky code that's easy to tear down, we aren't needlessly spending time thinking of the perfect architecture before we know what the problem is. In between two hills, we can spend some time looking at existing debts and decide which ones are ripe for paying off.

For more on the concept of Hills: https://www.youtube.com/watch?v=BD_zbXHgI8E

These are the currently planned hills. As you can see, it is quite a ways to go until we get anywhere close to our end goal. But hey, one step at a time!

As you can see, the hill that we are currently working on is called A Fort Wasn't Built in a Day. Here are the planned technical additions we plan to make during course of its development:

• AI: Goals, actions, sensors
• Day/night cycle
• Flecs Explorer improvements
• IMGUI
• Jolt physics debug/viz
• Modular buildings along splines
• Pathfinding with Recast and Detour
• Render architecture
• Shadows (sun)
• Simple atmosphere model
• Terrain stitching
• The Debuginator
• The-Forge based renderer

• Discord: https://discord.gg/rzByav6Y7Z
• Youtube: https://www.youtube.com/@tides-of-revival
• Itch.io: https://tides-of-revival.itch.io/tides-of-revival
• Open World Gamedev Newsletter: https://open-world-gamedev-newsletter.vercel.app/
• Twitter:
  • https://twitter.com/Srekel
  • https://twitter.com/gmodarelli
  • https://twitter.com/dryaddn
• Mastodon:
  • https://mastodon.gamedev.place/@srekel
  • https://mastodon.gamedev.place/@gmodarelli

It's impossible to build a game like Tides without a team. There is an incredible amount of things to do in a lot of different areas and dimensions. We value kindness, diversity, and avoiding stress. Poke me (Anders) on any of my channels if you're interested. :)

Only the source is stored on Github. All content is stored on a private SVN for cost and licensing issues. Let us know if you want to try building and running the game and we can help you out!