Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

As a Twine game, if it was using my example text-only scenario I put there, [EXPLORE] would simply just mean it'd roll a die where 4/5 of the possible rolls would be you finding nothing or getting a random good/bad event and the fifth would be a battle (maybe one at a disadvantage, like they get a free turn against you?), [LOOK FOR FIGHT] would either be a guaranteed fight, or maybe 4/5ths would be a fight and the other 1/5 being a random event pulled from the random event pool. [EXIT] could either be a guaranteed exit, or something like 2/5ths chance be exiting and 3/5ths being a fight. Just basic dice rolls. If I ever got off my ass and made a second game, I'd totally do something like this because there's NO way I'd actually code a real dungeon.

Since there'd be no actual dungeon, it'd just be a basic simulated "experience" of one, where entering means you don't heal after fights, but rewards are higher, and you lose everything if you lose a fight without exiting first.

(1 edit) (+1)

Thanks for your suggestions!

If I were to do a dungeon crawler, I’d want to fully commit to it and thoroughly study how to design it properly. For now, though, I probably won’t include it in the game, as it would significantly delay the plans for v0.0.4, the development of future 'mons, and require a lot of additional coding and polishing (as you mentioned, it would be quite complicated to implement  it nicely).

I already have some exciting ideas and plans for the combat rework in v0.0.4, and I want to try and focus on making that as polished and engaging as possible. Thanks again for your suggestion!