54 replies to this topic

[thudo]

Holy crap..

 

We finished voicing all of the Titan Guard too!

 

It was a... side project..

[fuggles]

I don't know what the future for this is. It was just a fun little project. The titans are largely how I imagined them as I could not get crewing working but the subsystem approach is unique at least.

The problem is throttling the power. I would be keen on using a feeeblade model but we can swap the little titan out of admech and put in the mechanicum one.

Nothing in stone, may be we don't bother.

[Roderick]

The I-nert's knight do you mean? It is closer to the looks of the actual knights and could be replaced in the Ad Mech as it was intended time ago. Many types of knights share the same pattern of suit which is the Questoris pattern (the common one). There are others which I don't know if they exist in models or if some 3d model has ever been made.

 

Lore wise, there are weaponless knight-like mechas called drovers:

 

A sub-class also exists called the Drovers who looked after the animal herds, as the nobility would not soil their hands with such work. The Drovers used walkers similar to those of their masters, but they were, by law, not armed with any weapons, despite the fact that they faced very serious threats in the form of predators and xenos raids. This forced the Drovers to rely on the Knights for protection, and created a dependency comfortable for the nobles, as it made revolt virtually impossible

 

I think the old model with big hands could be used for that role if there is such a necessity for a builder.

 

 

Besides, it's up to you if you want to focus on the Titans + ad mech with some knights or if the knights can be something on their own (besides, they can be featured in other imperial armies). Basically this is a choice between higher or lesser size and power. The scaling and progression is not easy but I found the subsystems activation a good thing to modulate the otherwise overpowerness.

Edited by Roderick, 09 December 2018 - 01:34 AM.

[fuggles]

I could call the builders drovers? I was planning on leaving the focus just on knights. It may be that you need some squads beyond the crew, or just make the crew better.

[Roderick]

That builder is quite different yet I like the model a lot. I think it is from the Age of Squat but I haven't seen it in the build I have.

 

For squads you need the scions (pilots) to ride the mecha and probably some homebrew supporting troops to engage and capture points. The crew for knights is just one person. Then you can keep the subsystems activations as the list of tasks of a single pilot.

 

I have always thought that knight worlders can have some old fashioned looks like cuirasses or like the Pope Swiss guard. They have low grade machines and usually count as pdfs but there's no much lore on them. Sacristans are the techpriests of these knights, not necessary augmented at all. I remember that Green scorpion made one model with the enginseer animation using the old man of the civilian models, so that it is factible to remake.

 

On the other hand, the pilots have a quite futuristic design with a helmet not far from any star wars trooper in the republic age. I'm sure there will be excellent proxies for them

 

Separating knights from titans you're detaching the Mechanicus influence. At the same time, depending on the knights available you get an easier scaling for the faction. For example, the knights only carry one titan grade weapon which should be the last tier upgrade choice.

 

This has the potential benefit of allowing a branchin branching between Imperial aligned house, Mechanicus aligned house and even Traitor aligned house. Extra pro is that you have teamcolours and badge/banner sets already known to paint the knights awesomely.

 

It all depends on the models at hand. Has someone got some idea of how many are?

 

BTW should knights be as slow as the current model?

Edited by Roderick, 09 December 2018 - 07:35 PM.

[thudo]

We're off topic but for an IK Mod to happen I would assume it would be like the relationship which Steel Legion possess: infantry as capturing and support while all vehicles (in this case, heavy walkers) do the lion share of the attack. T1 or early T2 start with Armigers (lesser nobles) as Scouts then move up the latter to more elite Knights.

 

Anyway, this is an ORKY thread folks.. if we want to start an IK faction thread I can do that but IKs are soo down the road.. voicing is nearly done however but this has been the way its always meant: voices go out way ahead of the projects.

[fuggles]

It's an admech thread? I can't make posts in a lot of places any more.

[thudo]

Ughh,,, sorry.. sheeshh when I read STOMP STOMP I thought this was Orky... hehehe..
 
So wait is the intent of this to have Titans or Knights as the main spearheads?

 

Also, tell me you plan to add these as we just finished voicing them?

Secutarii Hoplite
Secutarii Hoplite Alpha
Secutarii Peltast
Secutarii Peltast Alpha
Secutarii Axiarch

 

The VAs would did these also love anything to do with Legio Titanicus so they likely won't mind writing more.

[fuggles]

I think the intent is probably to shelve this? I mean it would be nice to get the AI going properly with the subsystems thing, but no-one seemed especially keen so on hold I guess.

[thudo]

We're busy with other items.. all in dat queue good sir.

[fuggles]

Ok, I think this is a viable route but the ai defeats me of getting the titans to upgrade themselves.

[fuggles]

As/when anyone can help I've done the unit info, loader and strategies. Started the add-on tactics but stumps me.

[Gambit]

What's the problem there?

[thudo]

I was still trying to figure that out as we have tons of different AI addon logic for tactic files back in '16 when UA and FoK did all that. Pretty much covered all eventualities.

[fuggles]

It's not one or another, it's a load of add-ons I want to build in a linear or possibly random order.

[Gambit]

Ah...

Then you must avoid the BO!!!

This should be done in the Build Flexible (...or in the tactic of the building with the addons )

Easy, just decide on the logic, and I will code it

Edited by Gambit, 20 April 2019 - 07:18 PM.

[thudo]

Why not just leverage it per unit tactic file via the Addons section of the EBPS? Its addons from units so best to handle it like we did for UA and FoK but using that tactic addon randomizer logic.

[fuggles]

Both of you just proved my point!

[fuggles]

This is where I am stuck - not sure what to do with the multiple addons, rather than the UM binary options:

 

Spoiler

----------------------------------------
-- File: 'LegioTitanicusScouttactic.ai'

class 'LegioTitanicusScoutTactic' (LegioTitanicusVehicleTactic)

LegioTitanicusScout = {}

function LegioTitanicusScoutTactic:__init( squad_ai ) super( squad_ai )

    self:SetName("Legio Titanicus Scout Tactic")
end

function LegioTitanicusScoutTactic:AutoBuildAddOn( addonSlot )
    for e in self.squad_ai:GetEntities() do
        local buildChannelLegioTitanicusScout = build_manager:GetBuildChannelFromID(e:GetID())
        if (buildChannelLegioTitanicusScout ~= nil) then
            local addOnID = buildChannelLegioTitanicusScout:GetItemIDAt(BuildChannelAI.PQ_AddOn, addonSlot)
            if (buildChannelLegioTitanicusScout:IsBuilding() == 0 and buildChannelLegioTitanicusScout:CanAddToQueue(BuildChannelAI.PQ_AddOn, addOnID) == BuildChannelAI.CANBUILD_Ok) then            
                buildChannelLegioTitanicusScout:BuildAddOn(addOnID)
                return
            end
        end
    end
    return
end

function LegioTitanicusScoutTactic:InitAbilities()

    if (LegioTitanicusScout.rally_id == nil) then
        LegioTitanicusScout.rally_id = cpu_manager.stats:GetAbilityID( "marines_rally" )    
    end
end


function LegioTitanicusInfantryTactic:CheckForBroken()

    if (self.squad_ai:IsBroken()) then
    
        -- Check if I can repair my morale
        local rally_id = cpu_manager.stats:GetAbilityID( "marines_rally" )
        if (self.squad_ai:CanDoAbility( rally_id )) then
            self.squad_ai:DoSpecialAbility( rally_id )
        end
    end
    
    -- Call basic broken check method
    InfantryTactic.CheckForBroken(self)
end

--[[function LegioTitanicusScoutTactic:DoAbilities()
--Only ability is rally which needs to be done when broken.
    if (self.squad_ai:IsAttacking() and self.squad_ai:CanDoAbility(LegioTitanicusScout.rally_id)) then
        Ability.DoAbilityTarget( self.squad_ai, LegioTitanicusScout.missile_id, Ability.Filters.CloseVehicleEnemy, 1 )
        Ability.DoAbilityTargetEntity( self.squad_ai, LegioTitanicusScout.missile_id, Ability.EntityFilters.CloseBaseEntityEnemy, 1 )
        Ability.DoAbilityTarget( self.squad_ai, LegioTitanicusScout.missile_id, Ability.Filters.CloseSquadEnemy, 4 )
    end

    -- Do basic abilities
    LegioTitanicusVehicleTactic.DoAbilities(self)
end
]]

function LegioTitanicusScoutTactic:Upgrade()
--[[
I assume that addon slot 1 is really 0? There is scope to play with these, depending on melee rush but shields first
    self:AutoBuildAddOn(0) -- engines/movement -- legio_titanicus_scout_addon_test1 -- should be built fifth
    self:AutoBuildAddOn(1) -- ranged weapons -- legio_titanicus_scout_addon_test2 -- should be built second
    self:AutoBuildAddOn(2) -- shields -- legio_titanicus_scout_addon_test3 -- should be built first
    self:AutoBuildAddOn(3) -- keen sight -- legio_titanicus_scout_addon_test4 -- as needed
    self:AutoBuildAddOn(4) -- melee -- legio_titanicus_scout_addon_test5 -- should be built fourth
    self:AutoBuildAddOn(5) -- abilities/shield recharge -- legio_titanicus_scout_addon_test6 - should be built third
    self:AutoBuildAddOn(6) -- missiles -- legio_titanicus_scout_addon_test7 -- as and when
]]

    -- Figure out my enemy's favourite class
    local enemy = cpu_manager:FindClosestEnemyPlayer()
        if (enemy == nil) then
            return
        end
    
    local class_type = enemy:GetMajorityClassType()
    
    -- Larkins hard counter upgrade for infantry
    -- But how on Earth do you make it have routes and options?
    if (class_type == UnitStatsAI.UC_LightInfantryLow) or
        (class_type == UnitStatsAI.UC_LightInfantryMed) or
        (class_type == UnitStatsAI.UC_LightInfantryHigh) or
        (class_type == UnitStatsAI.UC_HeavyInfantryMed) or
        (class_type == UnitStatsAI.UC_HeavyInfantryHigh) or
        (class_type == UnitStatsAI.UC_MonsterMed) then
            self:AutoBuildAddOn(0) -- Baal Predator    

    -- Larkins hard counter upgrade for Vehicles
    elseif (class_type == UnitStatsAI.UC_VehicleLow) or
        (class_type == UnitStatsAI.UC_VehicleMed) or
        (class_type == UnitStatsAI.UC_VehicleHigh) or
        (class_type == UnitStatsAI.UC_MonsterHigh) then
            self:AutoBuildAddOn(1) -- Annihilator Predator
    end
end    
 

 

[thudo]

Why not just do this then..
 
Posting the critical Upgrade() section where we want to specify the specific Addon Order then Add "3" and "6" at the end.

function LegioTitanicusScoutTactic:Upgrade()
--[[
There is scope to play with these, depending on melee rush but shields first
    self:AutoBuildAddOn(0) -- engines/movement -- legio_titanicus_scout_addon_test1 -- should be built fifth
    self:AutoBuildAddOn(1) -- ranged weapons -- legio_titanicus_scout_addon_test2 -- should be built second
    self:AutoBuildAddOn(2) -- shields -- legio_titanicus_scout_addon_test3 -- should be built first
    self:AutoBuildAddOn(3) -- keen sight -- legio_titanicus_scout_addon_test4 -- as needed
    self:AutoBuildAddOn(4) -- melee -- legio_titanicus_scout_addon_test5 -- should be built fourth
    self:AutoBuildAddOn(5) -- abilities/shield recharge -- legio_titanicus_scout_addon_test6 - should be built third
    self:AutoBuildAddOn(6) -- missiles -- legio_titanicus_scout_addon_test7 -- as and when
]]
        local myTable1 = {2, 1, 5, 4, 0}
        local num1 = math.random(1, table.getn(myTable1))
        local result1 = myTable1[num1]
        self:AutoBuildAddOn(result1)
        self:AutoBuildAddOn(3)    -- Keen Sight
        self:AutoBuildAddOn(6)    -- Missiles
end

You can also just merely forego the late two lines and lump them in also as follows:

local myTable1 = {2, 1, 5, 4, 0, 3, 6}
local num1 = math.random(1, table.getn(myTable1))
local result1 = myTable1[num1]
self:AutoBuildAddOn(result1)

Or even easier..

self:AutoBuildAddOn(2) -- Shields
self:AutoBuildAddOn(1) -- Ranged Weapons
self:AutoBuildAddOn(5) -- Shield Recharge
self:AutoBuildAddOn(4) -- Melee
self:AutoBuildAddOn(0) -- Engines
self:AutoBuildAddOn(3) -- Keen Sight
self:AutoBuildAddOn(6) -- Missiles

If a set sequence of addons need to go then the one above is the easiest.