new to the group - new roguelike

Hello,
It's my first post here, so I will introduce myself. My name is Bartek
Bojarowski and I am a student from Poland (Wroclaw, if anyone was
bothered). In my spare time I am working on an OO roguelike in java and
I would like to share my ideas about my game. The reason for doing so
is, of course, some feedback, be it positive or negative.
The whole game takes part in - one could say - overworld, i.e. you walk
through forest, deserts, plains, etc. then explore caverns or towns.
Therefore, I needed some nice way to show the map in a continous
manner, I did this by creating a Level consisting of 90x90 tiles (in
fact, these are 3x3 sublevels of 30x30 tiles), so when you walk deep
enough the map, the map recenters on you, so in fact, you cannot see
where one part of the map ends and other begins (omiting lags related
with loading further data). Each forest, swamp, etc. is generated in a
fully random manner, i.e. there is a certain probability for each tile
to be a tree, stone, mud and so it goes. However, the overmap is
generated in a 'fractal way'(don't know how to say it;p), so, all in
all, there is no such mix that once you travel one level of desert then
one level of forest then one level of swamp, and then one level of
desert. Also, when a tile is generated, the Level ('the' level, because
it is "static" so there is only one), as he is responsible for setting
tiles, moves a clone of this tile coordinates by (+/-rnd(0,9),
+/-rnd(0,9)) and asks a levelgenerator which would be responsible for
generation of this 'moved' tile to generate a tile(so there is no
clearly visible border when one moves from a forest to a desert).
Possibly I will do some fractal stuff with this later on, but for the
time being it's ok.

Everything which takes place in the game event driven. There is an
events queue, (which is a hashmap) and turn by turn it gets a linked
list of all events that are to happen during this turn and executes
them. Each monster generates whatToDoEvent which, when executed,
generates itself once again (after some time, depending on monster
speed) and asks monster Brain what to do? The brain (if it is a human
controlled monster) waits for the input from UI and translates into an
action - which I will describe later on. If the monster is controlled
by computer it asks it's brain to choose from potential actions (like
chase someone*, get some item*, attack*) the one which is most
important for the time being and executes the action - the action, when
executed, generates proper event which will be executed depending on
monster reaction time (this value is in fact very insignificant,
however, I added it, because it does not increase complexity and with
it without any problems one can easily add quite realistic state of
being drunk, by increasing the reaction time, or some weird monsters)-
like moveEntityEvent, or MonsterAttackEvent. This is what I have done
for now (however there is nothing interesting yet, as there are two
types of monsters and one type of item, and three potential actions for
monsters to do). My closest plans are connected with behaviour of
monsters, not to say AI, I want to implement some groupthinking - each
monster group will have a leader - the one with highest Cha and he will
tell monsters which actions to do. Next plan is some usage of items so
you can do something more than just pick them up. Next I want most of
events to generate signals, these will be a way by which a monster can
get a new potential action to do, if for example a goblin sees that a
previously neutral orc or sth attacks his friend - a signal - his brain
will get a new potential action like attack the orc, or when sb hears a
blast somewhere close, depending on his characteristics(curiosity,
courage or sth) he will get the potential action to check what was that
or escape from it, etc. So all monsters will be controlled by some high
level commands like 'go for the player', 'get the jewel'. I have some
further plans, but I will write about these when they will be in
realistic proximity to implement. Everything what I described is of
course some general outline of all the stuff and provided examples
might not be best. I am aware that simplicity is the key, however this
model, potentially confusing, seems very natural for me, it is easy to
add different ideas and, all in all, it works. If you are interested in
the code or itself or the game itself, You must wait until it is at
least a bit interesting, I don't want to show a roguelike skeleton
where You walk around encountering monsters moving in random
directions, although many people do so.

Tell me what You think, if You are aware of some common mistakes while
doing things which I described tell me, so I can omit them. This is not
my first roguelike project(I did one, frankly speaking quite big, in
qBasic eight years ago, however although I have the code, I've lost all
the data files, so it's not possible to play it), so I am aware of the
most common mistakes related to roguelike programming, what I would lke
most, are more specific comments.

*for example to describe the ChaseAction class -> it consists of an
actor (the monster who is chasing), a path(a map of coordinates in
which when you ask for the nest step you give your current position as
the key) and a target(another monster). When this object is created, it
generates a path(actor,target). This action upon execution checks if
next step is possible(if can be not, if for example another monster got
in actor's way) if it is not, it creates another path to the target.
Then the class creates a new MoveEntityEvent, with actor and
path.nextStep(currentCoord) as arguments. And there is a chance to
reevaluate the path, depending on the distance(actor, target), the
smaller the distance the greater the chance to do so. This is only a
temporary solution, as it makes all monsters see their target whether
they should see it or not.