UFOpaedia-friendly Celatid [UNIT] [OXCE]

[Kzer-Za]

I think the difficulty is already factored in by the amount of Celatids originally spawned in the map. Where on one level you would encounter 1 Celatid, on another you encounter, say 4. Each of them creates a clone every X turns, so the amount of clones is already proportional to the difficulty level. If I also increase their cloning rate with level, the difference between the levels will be too sharp. What "X" is equal to is another matter, this is debatable. I thought that if I made it less than three, then most players would see Celatids clone themselves too rarely. Besides, now they attack not so often as before, because, as I mentioned in the description, I thought that cloning should take some time, so on the cloning turn they have 50% TUs. But if people think that 3 turns is too frequent, I will decrease it. Perhaps, 5 turns?

Concerning the unused frames: that's a good idea, but can you explain how to use them? Since I can't draw, I didn't bother learning how to use existing sprites either. Also, there is the issue of the embryo sprite for inventory. Ok, for this I can repaint a stun bomb into green, perhaps. But I still would need a PNG of a stun bomb.

[Tiny Wisdom]

I think the difficulty is already factored in by the amount of Celatids originally spawned in the map. Where on one level you would encounter 1 Celatid, on another you encounter, say 4. Each of them creates a clone every X turns, so the amount of clones is already proportional to the difficulty level.

This is a good point that slipped my mind.

I used the battle generator to test it out but after the 3rd/4th turn the game crashed with the following error:

Code: [Select]

[FATAL] A fatal error has occurred: Invlid surface set 'BIGOBS.PCK' for item 'CELATID_CLONE_WEAPON': not enough frames
Either OXCE-5.6.2-1e89df63f-2019-08-15 isn't enough or you are missing something trivial in CELATID_CLONE_WEAPON.

Concerning the unused frames: that's a good idea, but can you explain how to use them? Since I can't draw, I didn't bother learning how to use existing sprites either. Also, there is the issue of the embryo sprite for inventory.

Download and extract MapView2 (also called OpenXCOM.Tools) from here.

Copy CELATID.PKG & CELATID.TAB from UFO\UNITS (so you are not directly modifying the game files) and open CELATID.PKG with PckView which is bundled with MapView2 (also called OpenXCOM.Tools) by navigating to File > "Open Pck (terrain/unit)".

When you are successful, you'll see something like this.

Now for some technical stuff, Celatids use drawing routine 9 and are in constant animations.

Referencing the relevant code here and here shows that their living sequence is hardcoded to start on frame 0 and end on frame 7 (8 frames altogether), whereas their death sequence simply starts on frame 25 and is limited to 3 frames by default (e.g. the death sequence could probably be from frame 25 to 50).

This means that to create new animation sequences for drawing routine 9, you need to define frames 0 to 7 and then frames 25 to 27 (i.e. frames 8 to 24 can be blank since they will be ignored anyway) and unless you increase the number of death frames (i.e. deathFrames).

PckView is surprisingly powerful and can accomplish this with relative ease.

Ok, for this I can repaint a stun bomb into green, perhaps. But I still would need a PNG of a stun bomb.

PckView lets you paint with pixel precision.

Just copy BIGOBS.PKG & BIGOBS.TAB from UFO\UNITS and open BIGOBS.PKG with with PckView by navigating to File > "Open Pck (bigobs)" where you'll find the stun bomb on frame 38.

Actually, you know what, I made some time and attached some proof of concepts (just to show it can be done). I only consider the repainted stun bomb "final" but the clone animation sequence from the Celatid egg/spore could definitely be more seamless.

Note: I used ImageMagick to turn a sequence of PNG files into GIF format since PckView can't do that. For the game you can just have a custom pair of PCK and TAB files.

Edit: I was able to fix the crash by replacing:

Code: [Select]

    builtInWeapons:
      - CELATID_CLONE_WEAPON
with:

Code: [Select]

    livingWeapon: true
and removing:

Code: [Select]

extraSprites:
  - type: X1.PCK

[Kzer-Za]

Concerning the crash with the CELATID_CLONE_WEAPON; that's strange, I tested  it on a nightly version 5.6.1 (v2019-08-03) and on 5.6.2 (v2019-08-28), both didn't crash. Maybe something was temporarily up with OXCE-5.6.2-1e89df63f-2019-08-15? Besides, I created this weapon by simply copying the rule of the original CELATID_WEAPON and decreasing the power and accuracy, since I wanted the clones to be slightly weaker than full-grown Celatids. So, maybe it was removing of

Code: [Select]

extraSprites:
  - type: X1.PCK

that fixed the issue? Though in my installation I didn't have problems with that. Could you please check if this issue is there with the latest nightly?

And thanks for the explanations on animations! I'll get to it in about a week, when I have some time again.

[Meridian]

Concerning the crash with the CELATID_CLONE_WEAPON; that's strange, I tested  it on a nightly version 5.6.1 (v2019-08-03) and on 5.6.2 (v2019-08-28), both didn't crash. Maybe something was temporarily up with OXCE-5.6.2-1e89df63f-2019-08-15? Besides, I created this weapon by simply copying the rule of the original CELATID_WEAPON and decreasing the power and accuracy, since I wanted the clones to be slightly weaker than full-grown Celatids. So, maybe it was removing of

Code: [Select]

extraSprites:
  - type: X1.PCK

that fixed the issue? Though in my installation I didn't have problems with that. Could you please check if this issue is there with the latest nightly?

And thanks for the explanations on animations! I'll get to it in about a week, when I have some time again.

probably incorrect reuse of bigobs from xcom1, read more here: https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Negative_indices_and_cross-referencing_other_mods

[Kzer-Za]

Strange that in my case everything is working, but to be on the safe side I replaced in CELATID_CLONE_WEAPON "bigSprite: 60" with "bigSprite: { mod: xcom1, index: 60 }".

[Tiny Wisdom]

Concerning the crash with the CELATID_CLONE_WEAPON; that's strange, I tested  it on a nightly version 5.6.1 (v2019-08-03) and on 5.6.2 (v2019-08-28), both didn't crash. Maybe something was temporarily up with OXCE-5.6.2-1e89df63f-2019-08-15? Besides, I created this weapon by simply copying the rule of the original CELATID_WEAPON and decreasing the power and accuracy, since I wanted the clones to be slightly weaker than full-grown Celatids. So, maybe it was removing of

Code: [Select]

extraSprites:
  - type: X1.PCK

that fixed the issue? Though in my installation I didn't have problems with that.

Technically what I had were 2 separate crashes with the same reason given.

The first crash happened on the 3rd turn and was fixed by removing the extraSprites section.

After that, the second crash happened on 4th turn and was fixed by defining livingWeapon.

I find it strange myself that this fixed it.

A couple things though... why is the extraSprites section there? X1.PCK contains the grenade animation which isn't used here. From what I see that section should be removed irregardless.

At first glance, the ruleset reference suggests that defining lvingWeapon won't work since it requires the "grenades" be marked as fixedWeapon which mean they can't be dropped but when I tested it, the cloning process still worked.

Could you please check if this issue is there with the latest nightly?

For the record, whatever is linked here is what I consider to be the latest OXCE "nightly". If you are building from scratch or using an unlinked version you'll probably only have a handful of people who will experience your mod as intended.

Which, incidentally, is why when I tested your Chryssalid tweaks, they all spawned dead.

Edit: I did some digging around and found https://lxnt.wtf/oxem/#/Extended which is labeled as "Latest version(s) for Linux" in the main post but also contains builds for Windows.

Either the main post should be updated or anything newer than 5.6.2-1e89df63f-2019-08-15 are "nightly nighties" and it might be a safe assumption that most are not using it.

Strange that in my case everything is working, but to be on the safe side I replaced in CELATID_CLONE_WEAPON "bigSprite: 60" with "bigSprite: { mod: xcom1, index: 60 }".

I reverted my changes and used this instead and everything worked as intended.

I still question the extraSprites section though.

I'll let you know how I fared after I encounter a Celatid.

That said... since I had some times I went quite a few rounds with your Celatids and I think 3 turns might just indeed be balanced.

However, I think the primary Celatids should act more like rear commanders. This means removing psiVision from the primaries and giving it to the clones instead. This prevents the primaries from charging towards possible targets and thus increases the possibility that they'll survive to create more clones.

But to make the primaries somewhat opportunistic, the primaries should be marked with sniper while the clones should be marked with spotter. This means that the primaries could potentially attack what the clones see.

I get that you are want the Celatids to be UFOpedia-friendly so if you are opposed to removing psiVision from them, consider reducing it by a bit less than half (like say 6) and take it as though the primaries are more resistant to human brain waves.

Just my two cents.

[Kzer-Za]

Maybe extrasprites is not really needed, I added it as a part of the patch that removed explosion animation from the "grenades" when they went off.

About making Celatid clones into spotters I'm apprehensive because, as far as I know, you can't limit spotters to relaying their information to only a certain type of units. I mean, it would be okay if they spotted only for primary Celatids (kind of psi-link between them), but if someone uses a mod in which, e.g. Muton navigators are snipers, then they (navigators) would also get information from the clones. That would, in my opinion, be unreasonable both from the "realism" point of view since Celatids are not sentient, and from the gameplay one since it would essentially give non-Celatid snipers psi-vision too (since Celatids would detect someone with psi-vision and relay that information to snipers).

To make primary Celatids more or less stay in hiding it's not necessary to decrease their psi-vision radius. We can just decrease their aggression to 1 or 0. I think, 1 would be okay, and I made this change, but I won't be able to test it for a week or so.

[Tiny Wisdom]

About making Celatid clones into spotters I'm apprehensive because, as far as I know, you can't limit spotters to relaying their information to only a certain type of units. I mean, it would be okay if they spotted only for primary Celatids (kind of psi-link between them), but if someone uses a mod in which, e.g. Muton navigators are snipers, then they (navigators) would also get information from the clones. That would, in my opinion, be unreasonable both from the "realism" point of view since Celatids are not sentient, and from the gameplay one since it would essentially give non-Celatid snipers psi-vision too (since Celatids would detect someone with psi-vision and relay that information to snipers).

I knew about this concern but I never experienced it myself so I left my theoretical changes in place until I encountered a Celatid.

And boy, oh boy... it was a slaughter. The clone Celatids took point and the Mutons rained reaction fire. I lost over half my troops (barely taking out 4 aliens in the process) before I noped out of there.

Definitely felt "cheaty".

To make primary Celatids more or less stay in hiding it's not necessary to decrease their psi-vision radius. We can just decrease their aggression to 1 or 0. I think, 1 would be okay, and I made this change, but I won't be able to test it for a week or so.

So yeah, unless the spotter/sniper values can be further restricted that idea is out the window.

I'm going to try reducing the aggression instead as you mentioned.

[N7Kopper]

A further lore-friendliness problem rears its head from the limitations of psiVision: Namely, the inability (unless the Wiki needs updating) to define specific units that can or can't be spotted by specific armour's psiVision at all, or by it in general other than through fearImmune. Celatids can detect human brainwaves according to the 'pedia, but would also be able to psisee dogs, Sectoid hybrids, Tau, elves, or whatever other player units you have in your modpack that are subject to morale rules. (and as an aside, that also means you'd have a harder time of making heroes who are immune to panic but can still be psi sensed, but I'm pretty sure that's possible by tinkering with bravery formulae)

But that is/was a limitation of OXCE, not a problem with this mod. Just wanted to mention it.

[Solarius Scorch]

Seeing people while not seeing elves or dogs reeks of BS anyway. I can't come up with a single explanation for it, apart from magic (probably poorly designed).

[Meridian]

Stunned celatid clone unit cannot be recovered alive, because the corresponding geoscape item is missing.

You can fix the mod by adding an item like this:

Code: [Select]

  - type: STR_CELATID_CLONE
    size: 0.0
    recover: true
    liveAlien: true
    costSell: 40000


[zee_ra]

Stunned celatid clone unit cannot be recovered alive, because the corresponding geoscape item is missing.

You can fix the mod by adding an item like this:

Code: [Select]

  - type: STR_CELATID_CLONE
    size: 0.0
    recover: true
    liveAlien: true
    costSell: 40000


Is there a way for me as a modder to know which specific frames in a given pck are missing?  Currently, the debug message states only that some frames are missing, but does not say which.

[TBeholder]

Cool! But let me point at the elephant in this room. That is, implications.
The floating system of Celatids is said to be a “naturally” grown anti-grav, rather than lighter-than-air. So it looks like they are mostly a bio-technological way to produce small antigrav units, moonlighting as a hunter-killer (as a side effect or with divergence from purely “industrial” breed). If captured alive, breeding and harvesting Celatids looks like a good way to churn out small (i.e. useful for hardware smaller than aircraft) antigrav modules without taxing your workshop and engineers. Perhaps setting up a Celatid farm would require something like a small-scale version of Mind Shield. Or maybe just use telepath minders.
Also, there are two possibilities:

• Celatids use Elerium.
  So it’s the “usual” Elerium-based antigrav, just biologically produced. In this case beside all other materials its reproduction is limited by having enough of Elerium to “refuel” the young. Mechanically perhaps Elerium would be “ammunition” for the spawning pseudo-weapon. Also, Elerium could be extracted from the Celatid corpses (or maybe from Elerium bladders dropped as “ammunition”).
• Celatids don’t use Elerium.
  Then their reproduction is not necessarily limited by exotic materials… but of course as a source of antigravity systems not dependent on Elerium they would become the second most important resource.

Also, can it feed itself? The fun option is yes, because then you could let them pick up items, and…

• If there is a way to customize item attraction (maybe with scripts?) make raw Elerium attractive for them, so in those rare cases when a Celatids is near Power Source broken by a shot (including its own), you either put it down very quickly or will be ears-deep in Celatids in a few turns.
• And/or just allow them to pick up the usual stuff per “Aliens Pick Up Weapons” standard mod, but have on-turn script to handle extraction of Elerium contents from the picked items that require it for production (such as plasma weapon magazines). That is, destroy the source item and “reload” the spawning pseudo-weapon or increase the reproduction readiness variable.

Destruction of raw Elerium or dropped alien artifacts would also give X-Com an incentive to neutralize the floating bladders ASAP.
Either way, if they tend to spawn soon after picking up objects, it will happen more often where the player can see their reproduction by fission (near broken stuff or downed armed aliens respectively).

Besides, now they attack not so often as before, because, as I mentioned in the description, I thought that cloning should take some time, so on the cloning turn they have 50% TUs.

 

However, I think the primary Celatids should act more like rear commanders. This means removing psiVision from the primaries and giving it to the clones instead. This prevents the primaries from charging towards possible targets and thus increases the possibility that they'll survive to create more clones.

That may be going too far. Just reducing the value (range) would make them less feisty.
But… if their actual (acid spit) weapon has limited ammunition (but gradually recharged on its own), they are going to run ahead less and hide more, right?
Also, the part with sack going down without green “blood” would look less weird for spawning than spitting animation. Is this k/o animation? Maybe just stun it in script (barely, so it recovers on the next round). So it’s given the “armed” spawning item, then knocked out, so it drops the item, which “goes off” and spawns?