Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Aukustus

Pages: [1]
The Temple of Torment is a open world Roguelike with stronger focus on roleplaying, good and evil choices and dialogues. Set on a fantasy world inhabitated only by humans invaded by forces of Hell.

I'd describe The Temple of Torment as mixture of Diablo 1, Baldur's Gates and ADOM.

As this turned from Beta to Stable game Early Dev forum was not enough.

Some things about the game
  • Full mouse support
  • Optional ASCII and Permanent Death
  • 28 World Map Locations, with many having sub-locations
  • Over 300 Unique Graphics
  • Character Classes: 125
  • Quests: 40
  • Over Hundred Items
  • Over 100 Spells and Talents (Passive and Active Talents)
  • Over 60 Monsters

Screenshots here:

Downloads here:

Design / Shops
« on: April 19, 2014, 05:15:03 PM »
I am designing shops for my game where players can buy equipment and I'd like to hear opinions for this system. My idea is to have something like shops in D&D games and Diablos.
  • Range of weapons with bonuses found in dungeon is -2 - +2. Players could buy +0 version of any weapon.
  • Players can buy the items which are available for loot at the time. More is added to shop when player gets deeper into the dungeon.
  • These shops would have every base weapon and armor in the game.

So my questions are:
  • There are class restrictions. Should fighter see spellbooks?
  • Is this system making the game too easy? The main idea is to get gear upgrades if player cannot find any in the dungeon.

Design / Spellcaster AI design
« on: January 28, 2014, 08:18:28 PM »
I was wondering about some basic AI for spellcaster monsters and I was thinking how to design the AI. On mana based systems do you make the monsters to use mana or do they have infinite mana? And how to they select what spell to cast?

I have quite limited programming skills so I was thinking about a AI that randomly picks one spell and uses it. Some impromevent to that would be if it picks fireball but the player is too close to it it would then choose another spell. Or if it selects confusion and player is already confused it would choose another spell.

I'd like to hear opinions about that AI or what kind of spellcaster AI systems there are.

Design / Class restrictions
« on: January 13, 2014, 03:53:44 PM »
What are your opinions on class restrictions? I mean like should sorcerer be able to use two-handed sword and plate mail or fighter be able to cast spells?

I'm designing three classes, fighter, rogue and sorcerer in my project and I'm not sure about how I would decide restrictions. My main influences are Diablo 1 and AD&D games and those two handle class restrictions opposite ways. I have strength, dexterity and intelligence as attributes. Strength adds 1 point to melee damage, dexterity adds 1 point to ranged damage and intelligence adds 1 point to spell damage.

I have three scenarios in my mind regarding class restrictions and their pros and cons:

1. No restrictions: Spells, armors and weapons are free for all. Spell casting classes would have more mana.

-Pros: More playing styles for classes
-Cons: For example fighter would be imbalanced while specialised in melee and laying destruction from far away with spells and then killing everything in melee that survived.

2. Some restrictions: Weapons, spells and armors have attribute requirements

-Pros: Same as 1. but more balanced, fighter specialising in intelligence would be less good in melee because of the missing points in strength.
-Cons: None came to mind.

3. Full restrictions: Fighter can use all weapons and armors, no spells. Rogue unable to use heaviest armors and weapons, no spells. Sorcerer unable to wear armor and weapons other than staff, all spells.

-Pros: makes each class wholly unique.
-Cons: less diverse playing styles for classes.

Early Dev / The Temple of Torment
« on: January 06, 2014, 08:51:21 PM »
Beta 13 is uploaded here:

I've been programming a roguelike for 5 months now with Python and libtcod and I decided to make a thread about it here also.

The Temple of Torment is a Diablo-esque roguelike with quests having good and evil choices. The character classes are fighter, rogue and sorcerer. The game is now about half-way done with now only sorcerer being not designed. About 80% of the dungeon is designed. Levels are done until abyss levels.

The game is sectioned into five parts: The temple, the catacombs, the caverns, the ruins and the abyss with each section having unique tileset and monster set. The temple contains demons, the catacombs contain undead, the caverns contain animals and demons, the ruins contain human cultists and the abyss having demons.

There are also two game modes: standard and hardcore, only difference being that hardcore overwrites the save on death, so this is the basic roguelike perma-death. Standard allows to load last save before death. At the moment pressing esc does not save game, so pressing continue in the main menu after pressing esc continues at last save, not from the moment the menu was entered. This will be fixed in later version.

Complete feature list can be found on website.


Programming / Maze algorithm in python libtcod rl
« on: September 11, 2013, 07:14:07 PM »
I have used the python tutorial from roguebasin for some time for my project and now I'm wondering how to make a maze. Since the dungeon builder is designed on filling the map and then carving rooms and drawing lines from center to center and maze generators seem to be made for printing. Does anybody have an idea how to implement an algorithm such as this?

Example code from Rosetta Code:
Code: [Select]
from random import shuffle, randrange
def make_maze(w = 16, h = 8):
vis = [[0] * w + [1] for _ in range(h)] + [[1] * (w + 1)]
ver = [["|  "] * w + ['|'] for _ in range(h)] + [[]]
hor = [["+--"] * w + ['+'] for _ in range(h + 1)]
def walk(x, y):
vis[y][x] = 1
d = [(x - 1, y), (x, y + 1), (x + 1, y), (x, y - 1)]
for (xx, yy) in d:
if vis[yy][xx]: continue
if xx == x: hor[max(y, yy)][x] = "+  "
if yy == y: ver[y][max(x, xx)] = "   "
walk(xx, yy)
walk(randrange(w), randrange(h))
for (a, b) in zip(hor, ver):
print(''.join(a + ['\n'] + b))

My dungeon building algorithm is make_map() from,_using_python%2Blibtcod,_part_13_code
Code: [Select]
1. Fill map with blocked tiles
2. Select random spot for first room and width and height
3. Carve room
4. Carve another
5. Join the rooms
6. Loop phases 2-5

I would like to be able to do the carving with using
Code: [Select]
            map[x][y].blocked = True
            map[x][y].block_sight = True

            map[x][y].blocked = False
            map[x][y].block_sight = False

Pages: [1]