You should really post this in the utilies subforum skoormit XD

Good idea.
Done.

Thanks for the input on my initial post and to address some of the points here, I wouldn't jettison the current way of handling replacements - in fact, I actively advocate keeping the current replacement model along with the new rebuild to template function. 

Utilizing the current system, I would do what I do now which is I create Replacement Battalions which I directly attach to my two Corp level Headquarters which manage my now six divisions of troops.  Whenever one of those divisions goes on campaign, I attach one of those Replacement Battalions (and Logistic Battalions) to go forward with them and as losses occur, I transfer from the replacement battalions.  Some fights I'm not losing much so those replacement battalions are able to cover the minor losses that occur and at some point I can rotate just those back.  Occasionally, I create new replacement battalions with the newer equipment for modernizing the force and transfer them to forward deployed forces to replace specific equipment and transport the old stuff back where I either destroy it or repurpose it - this is where the micro management hell really comes into play. 

Utilizing the rebuild to template, I've had horrible battles where Divisions have been shattered - or long sustained planet hopping campaigns where those Divisions have been reduced to 50% strength or less.  The number of replacement battalions would be too great and in those cases, I'm definitely rotating those units back from the front lines.  Realism wise, if a division has taken that much casualties it not only needs to take on new equipment, it needs to rest the veterans and then go through a train up with the new replacements and new equipment anyways which I figured would be 'factored' into the rebuild time anyways.

BL - with both options I would still have replacement battalions out there for routine combat loss and occasional forward deployed tech replacement - 'hey have you seen those new artillery pieces that just arrived? those will be useful' - but the rebuild the template system will be for my guys that just got mauled on Rigel VII or that one Brigade on Mars are still equipped with antique weapons so lets bring them back to Earth to bring them into the 27th Century.

Quote from: skoormit on Today at 07:12:34 AM

The query is limiting results to only show what one race knows.
And it chooses the most recently created player race.

At least, that's the intent, and it works in my games.
If you send me your db I'll dig into it.

Hmm, I see that Earth and Minerva have different ParentBodyIDs; Sol has 0 and Minerva has 3234.

Here's the fix:

Immediately after these lines:
inner JOIN
FCT_Star as str
on
str.StarID = ifnull(sb_parent.ParentBodyID,sb.ParentBodyID)

Insert these lines:
or
(
--special case for Sol
--default bodies in Sol (i.e. not Minerva) have a ParentBodyID of 0
--since we know that Sol is a single-star system, we can just take the star that matches the SystemID
ifnull(sb_parent.ParentBodyID,sb.ParentBodyID) = 0
AND
str.SystemID = sys.SystemID
)
Result should look like:
inner JOIN
FCT_Star as str
on
str.StarID = ifnull(sb_parent.ParentBodyID,sb.ParentBodyID)
or
(
--special case for Sol
--default bodies in Sol (i.e. not Minerva) have a ParentBodyID of 0
--since we know that Sol is a single-star system, we can just take the star that matches the SystemID
ifnull(sb_parent.ParentBodyID,sb.ParentBodyID) = 0
AND
str.SystemID = sys.SystemID
)
Let me know if anything still (or anything else) seems amiss.

You should really post this in the utilies subforum skoormit XD

I will make use of this one, thank you.