Messages

1

The X-Com Files / Re: [submod] X-Com Files: Kozinsky Stat Strings

« on: Today at 08:53:09 pm »

I suppose the latest version should work with bonus transformations like spartanism, or at least according to the changelog it should.

After transforming an already maxed-out soldier (field training wise) to infernal, the stat strings started showing room for improvement in almost every skill (except bravery, which is decreased). Yet in the next mission I tried to train these "missing skills" but received no improvement (as expected).

It seems as if when displaying what name + stat strings to show to the user it doesn't take into account stats after transformation bonuses (not sure if other bonuses) but rather compares them to the transformed soldier's currentStats? If this is the case, not sure if this is even fixable..? This is OXCE 7.15.

2

The X-Com Files / Re: Bugs, crashes, typos & bad taste

« on: Today at 06:18:20 pm »

Indeed you're right, but I already caught and fixed this issue.

Oh, you refer to https://github.com/SolariusScorch/XComFiles/commit/d63cb7aeb3daedfe332a59f57177b2468dfc04d0 I suppose. I don't quite understand how that would fix 10 hulls problem (or how they would end up happening in the first place), but I hope you're right and that is so. I suppose I'm going to award myself 10 osiron boxes..

3

The X-Com Files / Re: Bugs, crashes, typos & bad taste

« on: December 11, 2024, 09:04:17 pm »

In the snapshot, finishing the MIB attack on MAGMA base mission (which includes a MIB stealth bomber) gives you *10* MIB stealth bomber hull frames. I suspect it is intended to give only one, like with other enemy craft. I have no idea what would be the point of 10 identical frames anyway.

4

The X-Com Files / Re: No progress anymore. Do missed research?

« on: December 10, 2024, 09:58:51 pm »

You will need to post a save for anyone to be able to help you.

5

The X-Com Files / Re: Bugs, crashes, typos & bad taste

« on: December 08, 2024, 06:29:13 pm »

In the latest snapshot, USO text strings are missing (STR_USO_*_FRAME).

6

The X-Com Files / Re: Bugs, crashes, typos & bad taste

« on: December 07, 2024, 12:01:39 pm »

Not really a bug, but rather a suggestion for improvement. The base sell price for all veteran requisition rights is 90K. I think it would make sense that the price would be different for levels 1, 2, 3 and 4. For example, at least 1 could be somewhat lower, while at least 4 should perhaps be higher.

7

The X-Com Files / Re: Bugs, crashes, typos & bad taste

« on: December 02, 2024, 03:12:07 pm »

Black Moon (and likewise Blood Moon) mission has 150 despawn and zero abort penalty. There are 12 civilians. So if you go there and abort immediately, you get something like -180 penalty.

I think the penalties are always or almost always adjusted so that that going and aborting is not worse than letting the mission despawn. This is probably an oversight. Maybe the despawn penalty should be a little bit higher, like 250 or 300, like with many other civilian missions.

8

The X-Com Files / Re: Bugs, crashes, typos & bad taste

« on: November 30, 2024, 08:52:15 pm »

No sell price has been defined for wizkid rocket drone remains. This is probably an oversight, because essentially everything else has, and I suppose the scraps would be of some worth.

There seem to be maybe a couple of more similar STR_WRECKS, but at least for some of those it might be intentional (like the X-Com security camera).

9

OXCE Suggestions NEW / Re: [Suggestion] Display enemy movement range along with percentage of TU remaining

« on: November 30, 2024, 05:56:25 pm »

The player is not even supposed to know directly how much maximum TUs the enemy units have except through observation, so giving the game experience would run counter to that goal. As Yankes hinted, one of the big unknowns is also how much the enemy units have spent of their TUs - for example, can they still reaction fire if you move within their vision. Some other enemy unit stats can be learned after some research, though.

Of course many players will study these from the rulesets (etc.) or otherwise learn to approximate them, but this is not the same as providing the full-fledged GUI experience presupposing all this information.

10

The X-Com Files / Re: The X-Com Files - 3.5: Whispers In The Dark

« on: November 30, 2024, 05:51:09 pm »

Elite soldiers have 4x better CHOKE resistance compared to other humans and other soldier types. The only way to explain such a big difference would be some kind of partially protective gas mask or some such equipment. This is the same as MIB psi-ops, scientist, enforcer and executor, which also have a full or partial mask.

The sprites would be much more consistent with the stats if the sprites had some kind of mask or at least something covering the nose and mouth.

Now that I mention this, MIB stormtroopers are immune to CHOKE. Their corpse sprite seems to have something resembling a mask, but the big sprite does not.. I guess they removed the helmet while posing for the big sprite photoshoot..

11

The X-Com Files / Re: Bugs, crashes, typos & bad taste

« on: November 26, 2024, 05:01:08 pm »

Cound you please elaborate? I could use an extra pair of eyes, because mine seem desensitized by now.

I was mainly reacting to the commit message that was clearly upside down. Now that I look at it, I think the triggers work OK if the intent is to push off the Stakeout a little bit so that it does not occur quite as soon after you have researched Osiron through Surf Time. And that's fine, because prior to that change you would usually get started on theSyndicate arc well before dealing with the first level cults.

I also now realize that you can also get The Syndicate also through Osiron Fixer, for which there are more options (e.g. especially the cruise liner, because hacienda is such a rare event) than for the boss, so the impact should not be so big as I initially thought.

12

The X-Com Files / Re: Bugs, crashes, typos & bad taste

« on: November 26, 2024, 11:12:57 am »

Whatever you prefer. But I think you have to agree that current descriptions (at the least) are confusing and/or illogical in the order they will in practice be presented to the player. (I'd say the triggers are also inconsistent and illogical, but that's up to you.)

Surf Time description and briefing includes "This lovely beach is used by Osiron to distribute illegal alien tech". This presupposes that the player already knows what Osiron is. But the current situation is that the player has no idea what Osiron are at the point this mission pops up. And I don't know how the player would even know (or need to know) in advance of the mission who they are facing, unless there was some rumor about some secretive organization called osiron (similar to Zombie Implant Origins text below). Mininally I'd rephrase this for example like "This lovely beach is used by some goons to distribute illegal alien tech". The downside of this minimal approach is that the description is no longer fully accurate once you know (after the first mission) who those goons are. If this is bothersome, I guess you could include some rumor about a gang called Osiron there instead.

Zombie Implant Origins has the following:

Information from the EXALT Master allowed us to proceed with our investigation of the Zombie Trooper cerebral implant. Some unidentified person contacted the deep criminal underground last year with a very special request: to create a computer virus meant to infect psionic devices. This person struck some kind of deal with a group named Osiron, which claimed to know just the right people for this. Our further investigation confirmed this, and also suggested that the device to be infected could be the Zombie implant.
We need to check if any of our previous investigations gave us any leads. If yes, good. If not, our next step is to locate these Osiron people and ask them nicely about their mysterious client, and their provider. I'm sure M.A.G.M.A. will be very interested in obtaining this information. For this mission, we will have to use a civilian vehicle and concealable equipment.

This would need to be slightly rephrased, as the player will already know about Osiron by the time this is occuring. For example change "locate these Osiron people" to "locate an Osiron boss".

It might also be useful to highlight elsewhere the importance of capturing Osiron boss, because that is the primary gate for unlocking the essential Syndicate plotline.

13

The X-Com Files / Re: Bugs, crashes, typos & bad taste

« on: November 25, 2024, 07:07:38 pm »

Actually, STR_ZOMBIE_IMPLANT_ORIGINS is supposed to come before STR_OSIRON, as it serves as a gate to Osiron. But over the years more Osiron missions were added, and suddenly there are alternative routes to unlock Osiron.

Anyway, osironStakeoutSearch is a failsafe to ensure that if you have STR_ZOMBIE_IMPLANT_ORIGINS, but not STR_HUMAN_OSIRON_BOSS, then you get a high chance to roll this mission. If you have STR_HUMAN_OSIRON_BOSS researched, it uses the other, less common script osironStakeoutStandard.

The most likely route to get STR_OSIRON is through capturing a single goon from Surf Time, which has 22 % chance of spawning once you get surfer cover; after Promo III the chances decline.

Looking at my 3.5 game, I'm currently in May 1998 and I have had five Surf Time events already (months 7, 8, 10, 14, 16). I guess the RNG has been very bountiful for me. But even with normal RNG, you're very likely to get at least one Surf Time within a couple of months, 6 months at most. So if you play it right, you should have obtained STR_OSIRON by month 9-12 at the latest. Even if you don't do Surf Times or don't capture a lot of goons, you should have exhausted all the Secret Files topics around month 12 or so, which grants you STR_OSIRON. (Osiron Goons are actually an easy way to clean them up.)

Even if the initial idea has been to get to Osiron through the Zombie implant arc (after dealing with the Zombie MAGMA lab), etc. this is no longer the case at all.

Reducing the likelihood of Osiron Stakeouts through the actual primary path (STR_OSIRON) just delays the second phase of Osiron. The main goal of getting to the second phase of Osiron is guaranteed unlocking of the The Syndicate arc through Osiron Boss. This change essentially delays the syndicate arc a bit and makes it more RNG prone. Actually, as it stands, the best chance to get Osiron Boss appears to be to share the tritanium ammo with MAGMA, because then there is 25 % chance of getting tritanium ammo mission. which includes the boss. Apparently I should have shared the tritanium ammo tech to get this juicy mission. Doh.

I suppose you could either remove STR_OSIRON from Secret Files and reduce the chances of Surf Time considerably (to say, 5 % or less). This way unlocking STR_OSIRON would be much delayed unless you hit a RNG jackpot, like in your original concept.  Or you could redesign how osiron is introduced somewhat or maybe even keep the zombie plot path as a secondary backup path. With this latter option you could also more clearly separate the first-phase Osiron missions (goons and fixers) and second-phase osiron missions (to get the boss to get to the syndicate).

14

The X-Com Files / Re: Bugs, crashes, typos & bad taste

« on: November 25, 2024, 04:57:12 pm »

There is a logic error in commit "Osiron Stakeout is less common after Boss is researched" https://github.com/SolariusScorch/XComFiles/commit/26d6aa61c3f15e76f09e8cf1e8d64e828d6a30f7.
You decreased the chances of the osiron stakeout from 15 -> 5 % for the standard case which requires only STR_OSIRON true. There is another mission
osironStakeoutSearch which has the chances of 40 % yet which requires STR_ZOMBIE_IMPLANT_ORIGINS true and STR_HUMAN_OSIRON_BOSS false.

The problem here is that STR_ZOMBIE_IMPLANT_ORIGINS occurs much later in the game than getting STR_OSIRON, which you could get at month 5 or so already.

I was wondering why I have been waiting for almost a year for the stakeout mission after milking all the osiron goons are worth, and this is the explanation.

If the intent was actually to push stakeouts further down in the timeline, this is fine of course, but the commit message led me to believe otherwise.

15

OXCE Bugs / Re: [bug?] Changing the last armor's subtype does not work with mouse R-click

« on: November 24, 2024, 11:24:50 am »

Yes, we are miscommunicating. You don't need to change the armor to something completely different but rather the same previous one already known by R-click.

To demonstrate current behavior for example in XCF:

1) have two armored vests in the inventory; have two soldiers with no armor at all.
2) select armored vest/shield for soldier 1 manually (thus the game learns that the next R-click should be armored vest/shield)
3) at this point there is 1 armored vest in the inventory
4) right click soldier 2, and its armor is changed to armored vest/shield.

Alternatively:

1) have three armored vests in the inventory; have two soldiers already wearing armored vest (no shield)
2) select armored vest/shield for soldier 1 manually (thus the game learns that the next R-click should be armored vest/shield)
3) at this point there are 2 armored vests in the inventory
4) right click soldier 2, and its armor is changed to armored vest/shield.

This is the current behavior. You can change from unarmored to armored vest by R-click (first example) and you can change "armored vest" to "armored vest/shield" with R-click if there is at least one spare (second example).

Now, this is the behavior I'd prefer to have when there is no spare armored vest in the inventory.

1) two soldiers have armored vest/shield on them, zero armored vests in the inventory.
2) select armored vest (no shield) manually for soldier 1 (thus the game learns that the next R-click should be armored vest with no shield), like in the screenshot above.
3) at this point there are no spare armored vests in the inventory, but soldier 2 has "armored vest/shield".
4) right-click soldier 2, trying to change armored vest/shield to armored vest.
5) step 4/ does not work, because R-click depends on spare armored vest being in the inventory, it cannot change the armored vest subtype to the one engine learned in 2) and requested in 4).