PocketMatrix

I wrote a BIG LONG THING, then I deleted it.

Anyway, it depends on how bad-ass you want to be. If you want to go all out, go get a book on game "AI." I put AI in quotes because I am an AI snob, and don't consider game AI to be anything more than glorified state machines and if-blocks...but anyway...

If you just want to do a normal "AI" thing, you can assign properties to each monster (making each monster its own instantiated class is easiest). Then, per turn, tell it to update. The update can be as simple as checking distance relative to the character against some threshhold set as a property. This is the state machine method, and is pretty expandable.

We went over game AI a bit in a thread before (can't remember which).

Have a look at:



And see if that helps any.

RICoder's right though - a simple state machine for each monster class wouldn't be a bad plan at all... it all depends how "funky" you want to get

Cheers,

Refractor

oh boy this game just keeps getting better and better!

I knew I should have kept to simple puzzle games.....

I'm sure to "sell" attract more interest if there are actually thing in the game to kill....?

Heres my idea... create a enemy class.

load the map and for every location that has a partiuclar "enemy" add it to a linked list of "enemy classes", giving it details about where it starts etc... then just process the list every now and then ? then if it dies etc it should be a matter of just removing it from the list etc ?

-I've no idea... I PROGRAM PUZZLE GAMES.....

The usage of design patterns (singletons, managers, factories, etc) in games is covered quite well in "Game Architecture and design":



Cheers,

Refractor

Turing's test, meaning the test of AI as developed by Turing and extended by followers of such things.

But, moving on, I think this is a really interesting conversation to have. AI is one of those pet-projects I find myself wrapped up in from time to time.