Tempest Bot [v5_3]

[Derpduck [LORD]]

I think that they should have a chance of missing the rocket with air blast or sometimes not do it at all or else the will be OP

[Dusty]

hence the "random(3)" in that code snippet

[Lemonade]

It should also airblast too soon or too late instead of at right time or not at all. Like real players.

[Orpheon]

I intentionally didn't touch airblasting because it's damn hard to do, and the bot won't notice it's not shooting. No, this is not OP.
The ideal length is the length of the flamethrower+1 (for safety), aimDirection=point_direction(object.x, object.y, rocket_x, rocket_y)

I just need code that will detect an enemy rocket that's going to hit me, else the bot is going to do self damage.

big suggestion, not sure if you even want to or can consider it but

since usually human players are at least decently intelligent in finding enemies and objectives, why not have bots tag along with human friends upon occasion? like they need a "coop-feel" flag on respawn and have to get a human player to "squad" onto, and avoid following scouts if not a scout due to doublejump, and stop following a player that goes too far away, etc etc etc very complex but would make the bots verrrrry sexy because sometimes a teammate is all that a guy needs

honestly i would also make bots following based on the type of attack pattern they are performing, the type of teammate they are following (the class) and the enemy they are attacking (i.e. if its pyro buddy rips onto a heavy let's not go rushing in after as a sniper)

This is a brilliant idea.
I'll get to it.


Other than those two things, my future plans is getting that damn HumanVsBot mode working. For some reason clients can't join, which is not ideal. The hoster doesn't notice anything.
If someone knows why, go say it in the Help Thread.

PS: If you have any other suggestions, tell them.

[Orpheon]

Ok, thanks to Lorgan, I fixed the HumanVsBot mode.

Also included that follow-the-player and made it an option.

All friendly bots in range of 150 pixels around you (ca. twice a characters height) will follow you and jump when you jump. Unfortunately, they also often jump when they shouldn't.

Slower bots automatically don't follow you if you're a scout because they fall out of the range, so I didn't program class-checking.

Bots prioritize following over everything except fighting an enemy they can shoot at (in a line of sight). In those case they fight.

Links:
Exe
GMK


And for the airblast:

I just need code that will detect an enemy rocket that's going to hit me, else the bot is going to do self damage.

[Lorgan]

if distance_to_object(Rocket) <= 100 &&  owner.class == CLASS_PYRO{
    var target=-1;
    with(Rocket) {
        if team != other.player.team && collision_line(x,y,x+lengthdir_x(142,direction),y+lengthdir_y(142,direction),other.id,0,0) target=id;
    }
    if target != -1 {
        aimDirection=point_direction(x,y,target.x,target.y);
        code_that_calls_global.special;
    }
}

Something like that, but i'm not sure if it can check a collision with an id.

[Orpheon]

if distance_to_object(Rocket) <= 100 &&  owner.class == CLASS_PYRO{
    var target=-1;
    with(Rocket) {
        if team != other.player.team && collision_line(x,y,x+lengthdir_x(142,direction),y+lengthdir_y(142,direction),other.id,0,0) target=id;
    }
    if target != -1 {
        aimDirection=point_direction(x,y,target.x,target.y);
        code_that_calls_global.special;
    }
}

Something like that, but i'm not sure if it can check a collision with an id.

I did it like this, but I think the "< 5" is going to generate a hell lot of bugs.

Code:

with Rocket
{
    if team == other.team //I only want to calculate enemy rockets.
    {
        continue;
    }
   
    if point_distance(x, y, other.object.x, other.object.y) < 75
    {
        hs = other.object.x-x
        vs = other.object.y-y
        distance = sqrt(power(hs, 2)+power(vs, 2));

        factor = 13/distance //13=rocket_speed;
       
        hs *= factor //normalize the rocket-me vector, multiply it with 13 to make it the same length as the rocket speed, and compare the hspeed and vspeed.
        vs *= factor
       
        if distance > 42 and abs(hs-hspeed) < 5 and abs(vs-vspeed) < 5 //42=flamethrower_length; And I couldn't come up with something better to test whether the rocket is going to hit you.
        {
            //airblast
            other.RMB = 1
            aimDirection = point_direction(other.object.x, other.object.y, x, y)
            other.LMB = 0
        }
    }
}

[Orpheon]

I'm adding this to the download I just posted, and calling it v4_4.

-Added a working airblast

(Changes since first 2.3):
-Fixed HumanVsBot
-Created follow-human option.

Exe
GMK

[Unsung Hero]

 

Since this is synced I've been studying the intelligence of the AI to regular pubs.

The pubs aren't impressing me very much; I'm starting to prefer fighting bots.

[Orpheon]

Since this is synced I've been studying the intelligence of the AI to regular pubs.

The pubs aren't impressing me very much; I'm starting to prefer fighting bots.

Thanks.
Did you look at the last/previous match thread?

I hosted today a server called "Man Vs Machine: A/D". Yes, we did win. But it was close. We only won at the end by backcapping, but at standard "medic-centric combat" (strange since they had no medic) we simply got owned hard in the middle of the map.

Also, about the airblast: Clicking the right-mouse button right after firing won't work, and that's not different for the bots. They can airblast stupidly well if they're not firing (ie. not in close quarters), which is something most humans can as well. So I'm not adding random numbers until people really start to complain.


Next thing: FIX THAT GODDAMN MAP-CHANGIN BUG!!!

[Unsung Hero]

I don't believe there ARE medic bots.

[Orpheon]

I don't believe there ARE medic bots.

No, there aren't. Yet.

Yet.
The following code was a hell lot easier than I expected it to be.

What would be a medic priority healing list again (in exact terms)?

[Orpheon]

heal weakest first.

if you want realistic player replacements, make them stick with big guns and only heal others if no enemies are around

I don't want realistic player replacements, I want idealistic replacements.

-->The best players possible.

The only exception is the Sniper because that was simply not fun.
It's always easier to tone things down then make them better.

[trog]

Lowest hp > taking damage > heavy/soldier

I think if you go by lowest health percent it'll basically prioritize the medibuddy classes. Coding uber might be harder...

[Orpheon]

Lowest hp > taking damage > heavy/soldier

I think if you go by lowest health percent it'll basically prioritize the medibuddy classes. Coding uber might be harder...

Uber as soon as you get it or something.....

But no, I think I'll leave the medic alone for the moment. If someone wants to have a go at him, then I'll include it into the bot, but I want to make other things first.
One is fixing the thing that's hindering hosters most from hosting this (the map-changing bug), and the other is a surprise  .