Hello! My name is Edgar, I go as Redgar or "Red".
My passion for videogames comes from my love for living stories other than my own. You see, I had a sickly childhood, and whatever took me out of my own skin, was very much welcomed. And so, I met Role Playing Games.
Today, I'm no longer a child nor sickly, but RPGs are still what I love playing and making. I have many favorite games, for many different reasons. But I've decided to try and make a videogame that would be in a way, a homage for "Final Fantasy Tactics" Released back in 1997.
As I've mentioned before, I was a kid that enjoyed narrations (comics, books, movies, whatever could narrate an interesting story), either written by me or other's, because they would bring me into other worlds, so, when I learned about Isekai animes, watching those also became an obsession of sorts.
I'll use this post to talk about the game I'll be developing.
FAIR WARNING: I won't talk about the story because that'd be spoiling the fun, but I can talk about the mechanics and other stuff here. I'll make a roadmap based on my Game Design Document (which by the time I'm writing this, its unfinished, but you can read it here.)
---
What is "Isekai Chronicles"?
So, answering the main question here, Isekai Chronicles is a prototype (for now) of a game designed for mobile devices. It'll have some isekai elements to it, like manufacturing your own story, in a way. But it will also have heavy references from RPGs. If you find this answer short and lacking, keep reading, I'll explain the roadmap for the firtst three months. I'll just make a short pause to explain some progress indicators I'll be using through the roadmap,
Progress Indicators:
🔳 [PLANNED] - Means it has been planned, but it is still at risk of being cancelled.
❌ [CANCELLED] - Means It has been cancelled and won't be produced.
🟧 [NOT STARTED] - Means I may now start production, but I haven't started it yet.
🟨 [IN PROGRESS] - Means I've started working on this, but the work is not finished.
🟦 [TESTING] - Means the feature may be somewhat functional, but I don't consider it complete.
🟩 [COMPLETE] - Means the feature is complete, but I may tweak it a bit more to perfect it.
✅ [DONE] - Means I will not be working on the feature no more.
---
1st GOAL - SHORT TERM ROADMAP (1-3 Months)
CURRENT PROGRESS: [░ · · · · · · · · · ] %
I am well aware, this may not be a correct way to create a roadmap, but I'll make sure to update it accordingly as time goes by. Also, I may not produce everyhing displayed in the roadmap. The idea is that by the end of the third month. I have produced something that can be somewhat playable. Meaning. It would need to have a title screen, a new game button, a load button and (if really necessary) a settings button. Also, a minimalistic version of the core gameplay loop (available in the game design document inside the link I posted in the "fair warning" above). Here's a screenshot of the gameplay loop, the colors you'll see in the screenshot are not related to the "Progress Indicators" previously:

As you probably see, the gameplay loop has 4 stages (I've merged 1 and 5 into 1). I'll now explain what each stage and the main menu are supposed to be like by the end of the third month of production:
1. TITLE SCREEN
This will be the first screen of the game that should have a few buttons, maybe an animation, and that's it.
🟨1.1 Title Background, an image to be displayed at the main menu.
🟨1.2 Animated image, hovered over the background, something like a character or a portal.
🟨1.3 Legend saying "Touch to Start", to let the player now this is a touch screen enabled game.
🟧1.4 Start Journey Button, that woud let the player begin a new story.
🟧1.5 Load Journey Button, to load a saved game.
🔳1.6 Setting Button, to change language or possiby other elements of the game.
2. OUTFITTING
I need to divide this screen into three tabs. It's supposed to be used so that the player can prepare for the coming battle or quest.
2.1 STATUS
Will contain a screen with the player's recruited friends. If the people recruited are more than five, this is where the player decides who is part of his party. In the event he doesn't select anyone here, then the player will have to win combats alone. This screen also let the player dismiss members (meaning they will be lost forever).
🟧2.1.1 A background, for the Status window, divided in two sections, the smallest is the top, while the larges is the bottom.
🟧2.1.2 A frame, for character's portraits on the top, along with space to show the character's equpment and status.
🟧2.1.3 Portraits, for 6 types of characters.
🔳2.1.4 Icons, that will represent the character's status.
🟧2.1.5 Icons, to represent classes (beginer, melee, ranged and mage)
🟧2.1.6 A frame, to represent a member has been added to the party.
🟧2.1.7 Two buttons, one to accept and the other to cancel selection.
2.2 NEEDS
Some party members will have needs or quest to provide. This tab provides a space for the player to "chat" with its party members and see if he can get quest from them but also solve their needs.
🟧2.2.1 A background, dividided in threesecions, the top is to select a chracter, the middle is the the larger part, it will show something like an inn or a camp, depending on the location. The lower part will be for chat or messages to appear.
🟧2.2.1 A pair of larger portraits, one to represent the player's main character, and the second one to represent other characters
2.3 LOCAL SHOPS
The player may visit local shops.
NOTE: Shops will change or disappear depending on where the player is on the map. Say for example, if the player is at a mayor city, there'd be high chances to get different types of shops, but if the player is currently at a dungeon or the wild, it'd be a miracle to find a shop or vendor at all.
🟧2.3.1 A background, to display either a town, the widerness or some other region.
🟧2.3.1 A button, for each available shop.
🟧2.3.1 A list of items and its cons, to display when a shop has been selected.
🟧2.3.1 Two buttons, one made to buy and other made to sell.
3. EXPLORING
This will be a screen with a map, showing the different regions that the player can visit. Should there be any landmark that is greyed out or unavailable, it would mean there's nothing to visit or there're some pre-requisits to visit said place. Once the player selects a new location, a pop-up will display different exploring sites from the region. Upon selecting one, a cut-scene, a dialogue or a battle may be prompted.
🟧3.1 A background, to show the map.
🟧3.2 An icon, to be used as a landmark and display where the player's party at.
🟧3.3 A frame, to display a portrait in case it is neede.
🟧3.4 Another bakground, to display text if needed.
4. COMBAT
Battles will not necesarily define the story. But they are important to progress the player's abilities. Winning a combat may bring rewards,but losing one may also produce a reward of sorts. If the player decides so, he can order his party to flee the combat scene. Keep in mind this may produce penalties.
🟨4.1 Procedural gnerated arenas, for random combats. There will be also pre-created arenas or maps for specific combats.
🟧4.2 3D world elements like: walls, trees, rocks, etc.
🟧4.3 2D entities like: playable characters, enemies neutral entitie.
🟧4.4 Combat System, Tactic per turns.
- 🟧4.4.1 Menu with available actions per turn.
- 🟧4.4.2 AI Pathfinding that lets the character move a specific number of tiles from its original position.
5. REWARDS
When a battle ends, the player will receive rewards, but also notifications if a party member was killed in battle or if a defeated enemy wishes to join your party. If the player decided to end combat when the victor wasn't decided yet, this screen will also show some penalties, like your party members may express discomfort or some may even leave the party, depending on their specific situation.
🟧5.1 A background, divided in two sections. The top section will be shorter and used to display text.The second part to dispay recevied rewards or requests to join the party.
🟧5.2 A button, to accept all.
🟧5.3 Another button, to only accept loot.
🟧5.4 Another button to move to skip and go to the next screen. (2. OUTFITTING)
---
For now, this is my envisioned road for the first three months. Feel free to comment, criticize and provide any feedback. If you've reached this line in the post, I thank you for your time.











