Artificial Intelligence(In Progress) (Page 1 of 2)

Look into "Decision Trees" and "Finite State Machines" both easily done in Lua, and if you havent already done so study up on Coroutine's in lua.

A coroutine is similar to a thread (in the sense of multithreading): a line of execution, with its own stack, its own local variables, and its own instruction pointer; but sharing global variables and mostly anything else with other coroutines. The main difference between threads and coroutines is that, conceptually (or literally, in a multiprocessor machine), a program with threads runs several threads concurrently. Coroutines, on the other hand, are collaborative: A program with coroutines is, at any given time, running only one of its coroutines and this running coroutine only suspends its execution when it explicitly requests to be suspended.

If you need any help let me know.

Last edited by zester (2013-10-02 18:19:47)

hehe.

The cone thing is actually part of a larger physics based AI system (as far as the senses go) that I have thought up.

The cone represents the SIGHT of the object. Anything that collides with the cone is SEEN. Anything that isn't is NOT SEEN. So basically it is a Boolean affair. haha. ON, OFF.

Of course in Maratis it would be invisible and a ghost.

Well a "Decision Trees" is just a tree like so ...

emotion = {["happy"]=happy, [mad]=mad}

function mad(value)
    if value == 1 then
        --npc is mad and might do something about it
    end

    if value == 10 then
        -- npc is #%^ livid and will try to murder everything in its path
    end
end

that makes random choices, you might trigger it by way of a collision even say if another npc collides with this one.

A "Finite State Machines" keeps track of what "State" your npc is in at the moment as an example our above NPC might be in a murderous rage until he kills so many other npcs then its state might change to "Hunger" and the npc goes to the nearest pizza place mind you he is still covered in virtual blood, and has a couple of slices of pizza.

"Coroutines" are like threads what they do is allows multiple action to happen at the same time without the game having to stop and wait for an action to finish. You can just say do this and report back to me when your done. Or in otherword's as an example with the above npc "Kill all of the npc's around you and let me know when your done" - "ok now go eat pizza" - "Now sit outside and wait for the police". But while your geiving instruction to tho one particular npc you can do the same for 500 other npc's, all at the sametime.

And you could possible have some invisible particles that represent sound waves, until there is a collision event with those particles that npc police officer might not know your npc is butchering the local church group.

Last edited by zester (2013-10-02 21:05:16)

No problem, that's kinda what I like to do. I spend most of my day figuring out how to do something and then try to stream line it so others can pickup on it easily.

This is how my code looks so far:

Player = getObject("Player")
Head = getObject("Head")
eyes = getObject("Eyes")
text = getObject("Text")
text2 = getObject("Text2")
box = getObject("Box")
monkey = getObject("Monkey")
building = getObject("Building")

--SENSES
function See(object)
    if isCollisionBetween(eyes,object) then
        seenObject = getName(object)
        setText(text, "I see a ".. seenObject)
        seeing = true
   -- else setText(text,"I see nothing")
        --seeing = false
    end    
end

function Touch(object)
    if isCollisionBetween(Player,object) then
        touchedObject = getName(object)
        setText(text2, "I feel a ".. touchedObject)
        touching = true
    else setText(text2,"I feel nothing")
        touching = false
    end
end


--ACTIONS
function Jump(object)
    if seeing then
        setGravity({0,0,-4})
        addCentralForce(object,{0,0,9},"local")
    end
end
function onSceneUpdate
    See(box)
    Jump(Player)
    Touch(building)
    See(monkey)
end

Last edited by Tutorial Doctor (2014-03-02 01:57:11)

Thanks for the link, it my be of use if I decide to expand this out into a full AI system.

We had a big discussion on Gamedev.net about AI, and it seems a lot of people have definitions of AI. The definition I am sticking with is that intelligence is the ability to gather information, or it can be gathered information.

Most of what we know we use our senses to gather. Now, the extra part of intelligence is being able to use that information in meaningful ways. I just came upon a term called

I'm currently reading the second edition of "Artificial Intelligence for Games" by Ian Millington and John Funge which I must say is probably one of the best books on the topic of game AI. The authors have a solid background in and understanding of academic AI as well as game and simulation AI and discuss the differences between them.

The book is more or less a catalog of probably every AI technique employed today but also contain a discussion on how and why to choose specific techniques, advice on how not to overcomplicate things (simple AIs can behave remarkably intelligent compared to some more complex ones) with lots of examples from different games. It also discuss all the techniques and their applications in the context of a larger AI framework, basically how they can be combined and communicate in the AI subsystem of a game.

Last edited by Dahnielson (2014-03-02 18:33:14)

How about using a bool for the sound.

Maybe its a bug.

Just look where you end your if statement? You close the if statement End, then you add a variable, then an Else statement. and that the wrong part. I hope so.
Heres from the wiki:

Here is the project file:

https://sites.google.com/site/maratisfi … System.zip

Well, thanks anyway Akira_san, very much. I will just continue without the sound. Thanks again.