Yet another bot in teeworlds (Page 2 of 4)

Hi!
Very nice bot I've checked it in duel vs my last bot (unfinished yet too), and my one wins (current score: 144:100) But my bot still cannot use hammer properly (i'm trying to improve movements, not shooting), and cannot properly move on large maps with holes like ctf5 (because i'm not using waypoints).
Demo: https://drive.google.com/file/d/0BzwisF … sp=sharing
If you want, PM or Skype me (skype: ertaquo) and i'll give you last stable sources

Teeworlds has too little strategy for it to be as interesting as Starcraft bots imo. This is not just a matter of community size.

Update:
I added econ for the bot using server econ. This may be used to control bots presence with telnet and thus change the number of bots with a script such as teebot
That's not the case atm but i may configure it on my server.

For this kind of use, i prefer that server admins contact me by pm/mail since i'm resource limited so i can't spawn as bots as i want.
But, since i will write a script to managed my bots on my servers, i may make another script to mix your idea and mine in order to control my bots spawn and make it easy.

Edit: if a server allow bots, some evil mind will ask for several bot() without the server admin permission.

Hm, I will not release the source unless tw community/devs agree with this.
But if you want to use the source to make some thing similar and more suited to your goal, I can send you the code.

I think making serverside-style (implemented via your headless client) OpenFNG bots would be awesome. The thing about these bots being used by "hackers" is that they'd get banned quite quickly via vote, and where they're prevalent (public vanilla/whatever servers) kick ban votes are enabled, so it should really not be an issue. it's also quite detectable compared to aimbots, for example, so it should be fine. Also imagine the FPS lag on a mid-range PC with these advanced bots? Hella not worth it in the long run, other bot clients are better for their purposes.

On the subject of asking for bot() to join the server, you could make it so if in the title it has "bot() join" then it would allow itself to join, otherwise it wouldnt let itself go on.. and only admins/mods could set the title to allow it

I don't remember if this has been said or if you bot does this. But could you add an accuracy rate parameter?  I think I was playing with an illegal bot last night.  The thing that sucks about bots is how accurate they are and how fast they fire.  Your going to die in a second with a bot.  But with humans we have to adjust our aim and then when we think we will hit our target we will pull the trigger... some times.. others we just blind rapid fire hoping we his anything.

I think it would make the bot better and suck less if its accuracy rate and fire rate varied.

like pelya showed above  "Mr. Death" could be very accurate and use rapid fire while Harmless bots will miss all the time and won't fire as rapid.

Since i m trying to play with learning AI from scratch (since i know nothing like john snow) + holidays, i didn't work as much as i though i would. Currently I m wondering if i'll push all this on github.

To be short, why ?

Server side bot framework and scripting interface (Lua?) for different AI types is / would be cool. I don't use Lua yet.

But my hook moving is still far from rand()'s.

Coding aim bot and auto player hook from scratch is almost as easy as implementing one from someone's code (without help / tutorial). Other features wouldn't give you so obvious advantage over other non-perfect players.

Go have a look on Counter-Strike: Tee Time server. The auto balancing is bad but bots worth trying out.

Ok, some update.
I m working on automanaging teebots for the two features you suggest on this post :
- Join/Leave according to real player number : ex there is 4 bots max on the server, bots leave when nobody is connected and join when one player joins, bots leave one by one to let humans play when there is more than 9 clients (bots+human)
- web service with 16 bots to borrow bots (with a check, [allow_bot] in the name of the service)

Then, i have to clean the bot source and comment it (at least basic comments) before pushing it on github.