Lets Fix Team Events Once and For All for DSL

[Classicus]

Hi all, I'm looking to fix the team events for DSL.


1. Does rotate.bat from starcore work for dsl?


2.How do I get it to select bots past the first 3 of a team?


I think I can configure the events file and put better/more realistic events in, I found one with compressor fixed (thanks).


Might be a worthwhile thing to do. Events are fun but badly executed by the developers. Lets fix it perhaps.


Anyone interested?

[Gazea2]

1. Yes it should
2. Not possible without editing the .exe or whatever. The original AI teams only have 3 bots per team: 1 LW, 1 MW and 1 HW. That's why it only chooses the first 3 from each team.

[Classicus]

For point two I've been searching old threads and I've found https://gametechmods.com/forums/index.php/topic,1071.0.html

I don't know if this was ever completed/fixed ro whatever as I found a lot of it difficult to follow.

[HurricaneAndrew]

Good find there... Didn't know it existed. It's probably hard to follow just because philetbabe doesn't speak english very well.

[Classicus]

I made the .bat file for the code they talk about as far as I can tell it does nothing. It would be easier just to go back to doing tournaments like I was doing before but I really like the idea of your bot being slowly attrited during tournaments.

[Trovaner]

I've never used Philetbabe's bot rotator but there is no reason that we couldn't get it to work; batch files are pretty easy to use and write. There are however problems with using something like this. If Bot3, Bot4, and Bot5 aren't a lightweight, mediumweight, and heavyweight then you may end up fighting a SHW with your AW.

The optimal solution would be to write a program that c the weight classes of all the bots and compares them to the weight class of the bot that you are trying to use in the event. Unfortunately, I do not know how to call a function when an event/button is started in game (the EXE regulates this sort of thing).

[Classicus]

Maybe a new perspective is needed. Something different such as all heavyweights, middleweights and lightweights together in teams. Or something like the getting the game to see the first 3 and second 3 bots as two separate teams. I'm by no means an expert but can't we change it so that the game counts in 3's instead of 6's for bots per team? Or perhaps rearrange the bots 3 to a team and have the rotate.bat or a version of it as standard for DSL.

I know its a lot of work but it would be really great to have DSL with a functioning and usable season mode.




Additional:


The more I think about it, the 3 bots per team idea seems the most logical and do-able. I've read in old posts of games with 90+ AI teams so could be good.  Any thoughts?

[Mr. AS]

allow me to go off into a tangent about a problem that your going to encounter when you get your bots successfully into rotation---
while i appreciate your efforts, team events are always going to be "broken"/unbalanced (----) in some way shape in form dispite what bots you use.

lets say you have a bot with a single razor tip (botA), and a bot with a dsl hammer4 (botB)
you put botA into a fight against a given opponent, and the razor breaks off. you win the match (how you win when youve already been deweaponed isnt of any importance for this). the single razor takes 20 mins to repair.

now you put botB in there, you eventually get the hammer ripped off and you still win
the catch is- both weapons take 20:00 min to repair when its broken off, dispite what hp it may have, weather it be a poly extender or a overkill wedge, the game mode will still be broken and

as for rotate.bat i think starcore ai used some special files for the teams to "rotate" (does that file in the ai folder thats like .starcorebindings or whatever have to do with it ?), but i never really took much advantage of the file so i haven't much idea

EDIT: i suppose you could attempt at inserting PB's coding into the ai/wherever its supposed to go, i will have to look into how well it functions. but like trov said, you will have to have bot3/4/5 be consistent (aw, bw, shw OR lw, mw, hw etc), shouldnt be a problem with say dsl 2.1 ai if you wanted to switch the events from default dsl bots to the reps and back