You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 18, 2019. It is now read-only.
It'd be way easier to just start you off in the forest with a popup giving you the story. Same way Rimworld, Stellaris, etc do it. I can't think if any drawbacks to doing it that way.
Can you ensure the player doesn't get mobbed on turn 2-3 if starting in the forest? I used to start the player in a normal dungeon map, too, but then players complained about getting mobbed on turn 3...
Yea, could have a radius around the player that monsters aren't allowed to spawn during world gen. That would give the player a lot of turns to not be attacked, and doesn't seem too hard to do.
A starting village does seem cooler, though, just not sure there's much of a use for it. Besides someone telling you the story there's no other friendly NPCs in the game, backtracking isn't necessary, etc.
This got me thinking about the end goal, though. The end goal of the game is to rescue someone from Xibalba.
With starting village
Once you've rescued them, take them back to the village to win
As it is now, nothing respawns so taking them backtracking would be a boring waste of time
Without starting village
Once you've rescued them you win
No useless backtracking
So with that, no starting village sounds better. But, it might be cool to go with the first option and as you're back tracking through the caves and forests demons from Xibalba spawn to try and stop you from making it back.
Not sure what all reasons there would be to have this, except to have a chief to tell you the story before you head out into the jungle.
After he tells you, you can either Accept or Decline to go. If you Decline it goes back to main menu.
Maybe you start in your home, a chest near your bed contains your starting items.
The text was updated successfully, but these errors were encountered: