Dynaverse.net
Taldrenites => Dynaverse II Experiences => Topic started by: NuclearWessels on October 12, 2006, 05:09:58 pm
-
:cuss: :banghead: Stupid bloody browsers that crash when I've spent 20 minutes writing a post :banghead: :cuss:
Anyway, the way the AI is generated in my warp-disengagement missions is as follows:
If it is a PvP matchup then no AI is generated except in planet/base assaults/defenses, in which case the planet/base (should) be generated.
If you are flying against the AI (whether solo or with wings) then the AI is determined as follows:
- the BPV of the human controlled ships is determined
- some additional AI may or may not be added to your side
- an enemy AI fleet is created with an appropriate total BPV, more-or-less randomly carved up into one or more ships (e.g. a 300 bpv fleet would sometimes get allocated as 2x150, sometimes as 1x300, sometimes as 70+100+130, etc etc)
The point is, it was put together pretty quickly and is all BPV driven.
I'd like to come up with a scheme that uses more traditional ship groupings, but without restricting whatever madness the admins might inflict on their shiplist <looks at a certain Gorn>
I think that means it needs to be based on the shiplist categories of hull type, class type, special role, and bpv (and of course be in yfa/yla range).
Since some of you have clearly put a lot of though into OOBs, I want to snag some of your thoughts before I go nuts trying to create the new AI fleet generation scheme.
dave
<we now return you to the great turkey and bsg debates ;D >
-
I'd like to come up with a scheme that uses more traditional ship groupings, but without restricting whatever madness the admins might inflict on their shiplist <looks at a certain Gorn>
Quick and dirty? Have the missions never Pull Carriers or Escorts. The rest should be fine
-
Which ship creatin method are you using Dave? Has timewarping been solved yet?
-
Which ship creatin method are you using Dave? Has timewarping been solved yet?
Homegrown - I examine the human and AI ships drafted then read the shiplist to determine bounds on the YFA/YLA. I then discard all ships outside the date range, discard the drafted AI, and proceed from what's left. There are times when it will generate AI ships that should have been mothballed (if all 12+ human and AI ships drafted have a YFA that is earlier than the current year and the ships the creation routine picks happen to have a YLA that falls into that gap) but it's guaranteed never to pick a "future" ship.
dave
-
I see, so you are generating specific ships using their designation, eg "F-CA"
Are you using Mag's shiplist utiliy?
-
I see, so you are generating specific ships using their designation, eg "F-CA"
Exactly
Are you using Mag's shiplist utiliy?
No - it's a wonderful general-purpose utility, but since I was after a very small/specialized subset I wrote a custom one that cuts down on both the time and memory overhead.
dave
-
Quick and dirty? Have the missions never Pull Carriers or Escorts. The rest should be fine
;D
-
Is that done from within the script? Are you reading in the shiplist?
-
Is that done from within the script? Are you reading in the shiplist?
yeppers on both counts
dave
-
Good job Dave :)