Hi everyone,

I've started a project that should deliver a small openarena client capable
of interfacing with external bots written in Java and Erlang. My current
approach is to start from a plain client, keep any map/world code, VM and
network connection code, and replace any ouput devices (screen/audio) and
input devices (mouse/keyboard) with a mssage queue that will connect the
Erlang and Java VMs. At first both this "minimal client" and the external VM
will run in their separate processes, but in the end they should use a queue
shared by two separate threads. This should also allow easier and faster
queries about the world state (how many opponents the bot detects, etc).

I would like to know if you consider this approach as correct, and whether
you could give me some advice about the parts to replace. I know (or rather
suspect) that the specific commands (cvars?) will be game-dependent, but I
hope you could provide me with specific insights about customising the
engine.

Thanks a lot, and greetings,

Javier
_______________________________________________
ioquake3 mailing list
[email protected]
http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org
By sending this message I agree to love ioquake3 and libsdl.

Reply via email to