Pavonis Interactive Forums

I just checked in a fix for this today, will be in 1.5. Alien Hunters introduced an alternative path to unlock this project, so we had to disable it there too. That plus a bug in the disabling config for the primary path caused it to show up in the research list instead of the proving ground.

I can't comment on the balance aspect, but I can say that both supply convoy and defend were bugged in 1.3 and 1.4, causing the wrong reinforcements to drop and also causing them to drop far closer to your squad than intended. In 1.5 they will drop father away, but not necessarily out of vision.

Both of these are vanilla bugs, but we may be able to address them. We did something similar already for turret wrecks you end the mission without killing and for faceless you manage to kill before they transform, so there is precedent for granting corpses for units that are MCed when the mission en...

That does sound awfully inconsistent, and the behavior will depend on how the abilities were implemented, which doesn't seem right. We'll have to discuss with design (aka JL) about what the intent is here.

I'll take a look at that save, please send me a link. There was a bug here in 1.3 that was fixed in 1.4, but it shouldn't require a new campaign.

As for the first question, the rocket launcher and flame thrower abilities are not attached to the technical class, they're attached to the gauntlet secondary weapon. Look in X2Item_LWGauntlet.CreateTemplate_Gauntlet_Conventional() (for example): Template.Abilities.AddItem('LWRocketLauncher'); Templ...

Ok, I can repro the problem with your saves, but I think this is a side-effect of another bug that I posted about before and that we've already fixed for 1.5. The defend mission script had some bugs that caused the wrong reinforcement schedule to be used, as well as trying to drop the reinforcements...

I don't really want to get too far into the weeds of crafting a carefully worded description that precisely describes the reaction fire mechanics only to have it get lost in the translations to other languages :) The rough rule for OW is that it triggers when a unit enters a tile the shooter can see...

Are you using a strip weapons/items mod or the buttons included in LW2? The ones that are included in LW2 should not strip items from haven advisers. If they are, that's a bug - they are considered to be on a mission much like infiltrating soldiers.

Thanks for the detailed info. I'll take a look at this one next - please leave the save up for now. I'm finishing up some other bug reports before I'll get to this one.

Thanks for this report. There is a known bug in 1.4 with effects not ticking correctly on a mind-controlled unit after it returns to your side, leading to things like permanent stun/disorient/etc. We have a fix for this in 1.5, and your situation sounds like another example of this bug.

Some more thoughts on this: It seems to me that one of the fundamental issues here is that the cone is highlighting both the tiles and the units. This is misleading, because killzone doesn't target units at all! Only the tiles matter, and as for regular overwatch, a unit needs to move through a tile...

Thank you for the very detailed analysis & save game Alketi, this was very helpful and saved me a lot of time. I agree that killzone shouldn't be lying to you about which targets are affected, regardless of which direction they run. I'll see what i can do about fixing it.

You can move aliens around, yes. \AiDebugAi to show info about each unit, including their object ID (its near the top of the unit, not the XGUnit_XX one). Use \TeleportUnitIDToCursor <id> to move a particular unit to the cursor.

Thanks for the tip, LordYanaek. I'll try some auto-fills to to try provoke it.

Thanks for the save! The \savescum console command will adjust the random seed so you can get different results after a reload, so I'll do that until I can get a panic.

Thanks, I'd appreciate the saves if you can get some. The way the game detects if a unit moved is a bit weird to explain, so if they had moved with their last action the previous turn it may still consider them as moved for the purposes of the peek check if they shoot with their first action the nex...

There are a couple of bugs in the defend and supply convoy missions in 1.3 and 1.4. We have fixed them for 1.5. First the missions were using the wrong reinforcement schedules - they use the standard timed reinforcement schedules instead of the specific ones defined for these missions. The timed one...

The panicked leader triggering the bug sounds like a likely culprit, but I'm not sure it's necessarily concealment related. The earlier bug that we fixed was way back in 1.1 (I think?) and was related to pod leaders scampering before concealment broke, so they didn't know where XCOM was and would fl...

Try uncommenting this line in XComUI.ini, and change it to true:

Having saves would certainly help for the cases where it's reproducible. Some of them seem to fix themselves after a reload, and that class of cover bug will be extremely difficult to pin down unless someone can figure out exact steps to make it happen consistently. The PCS eating bug was like this ...

This sounds like one of the vanilla bugs with cover. There may not be much we can do about these, unfortunately, but I have been busy enough with the bugs we know to be LW2 bugs that we can fix that I haven't had time to look into more speculative stuff lately. Cover bugs are one thing that I would ...

Thanks for the save! This one is pretty fascinating, because it looks like there are two separate bugs here. The sword slice bug actually appears harmless: it's just a visualization bug in the Whirlwind shinobi perk. When the mission starts the passive effect gets applied to the shinobi, which was i...

If it's reproducible can you send me a link to the save please?

Found it, thanks! Looks to be a bug with iron skin where if the incoming damage is less than the damage resistance, you heal the difference. Will get a fix into 1.5.