Like I said, this mod uses standard reinforcement and encounter mechanics, so whatever is breaking isn't specifically this mod. Without knowing the modlist of the users having this issue, i can't tell you anything else.

please check if this mod is in use.

https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2075465256&searchtext=cap

also please check number of units currently in play (including xcom) - if the number is 50 or above, reinforcements will not spawn as that is the unit cap. the above mod actually reduces this cap to 20. whether hitting this cap could cause ids to not be found i don't know, but this would explain any intermittent non-spawn behaviour

That mods not in use because the behaviour cap in testing has been set to 100, and not all spawning mechanics are being effected: specifically, only those from hack templates and abilities used within AI trees.

FTB helped resolve a similar issue prior when working with Dark Event Manager - turned out users were using a pirated copy of the game. Surprise.

Thank you for your time. Mainly just trying to diagnose why the encounter lists are not being picked up - as whatever's effecting this, is effecting other mods that have worked fine for so long that this sudden failstate across the board has been blindsiding.

Regardless, thanks anyway, and look forward to your contined work =) - Remind us to buy you a pint sometime =)

@MrCloista - This is one of the other mods effected, that on surface level seems to use similar configuation and is likely being effected by whatever is effecting DB too. If we find anything will pass along, as quite possible something's borking something in UE just as easily as anything ModBuddy tries to compile.

Extended Hacking Effects

@Leyshade interesting. Sounds like something is breaking specifically the +Reinforcement part of hack rewards.

Are the people with issues running LWOTC? I don't and never have run it and I don't build for compatibility with it because it changes so much under the hood. Wouldn't surprise me if it's the root cause.

@MrCloista - Nope, no LWOTC. That thing is a convoluted mess in our opinion, and could use some serious optimisation and streamlining to prevent it's house of cards falling down as often as our own. We assure you, if it involved LWOTC, we'd be shipping people straight off to Kiruka who's their resident idol.

Only thing that's changed from the end user perspective we're working with is the endless updates to AHW content by Reshi (bless them, they're practically a machine), and restoration of a whole bunch of missing packages in an extension to this mod and this mod being worked on that the community desperately needs someone to upload. But we don't see how either of those changes could have detonated the ability for +reinforcements to fail to pick up any of the encounters they list.

Trying to contact Reshi, but they're probably somewhere scheming with Syusa on how to make more people suffer true pain, and did reach out ot others effected, but no joy as yet.

£5 bets it's going to be something really dumb by the end of this. Still owe ya a pint either way =)

The other obvious answer is UECP as it nukes encounter lists.

https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=3034030070


Is the obvious issue.


Reshi's stuff is fine I use it myself.

Right, this is going to seem like a really stupid question, that probably should of been asked before but didn't occour to us until now.

Does +reinforcements have a tie to bBadThing=, because several of these were looking at have been changed from positives to negatives, with the associated encounters placing units into eTeam_Resistance and eTeam_Xcom.

Just loaded with the encounters changed to the buckets from Raider Bases[http//1601260788] (was lazy, first folder clicked on) and it's picking those up, but not the ones from the effected mods or base game itself.

Update: Futher tested with encounters from other mods - doesn't pick up anything other than Raider Bases buckets, the AHW encounters (tested various), and a handful of base game encounters.

RE: UECP - We don't personally use it after realising it compiled others work without credit, including their typographical mistakes, so shouldn't be a concern for ourselves.

Going to run a UE diagnostic and make sure that it's not something in engine compile on game load that's causing the issue, to narrow it down from that end. THanks again for your time and patience, it's reassuring to know that some issues are probably because of out of date tech.

so your making changes to this mods configs and things are breaking?
can you try an unsub/resub to reset your configs and see if this mod works, in an unedited state.

encounter list configs are something real easy to completely mess up

@MrCloista - We have seperate configs for our own project where this issue doesn't occour. Suggested they resubbed and the issue persists on their own systems.

This doesn't occour on our own system with our own configuration, but is replicateable on their system regardless of what configs are used. That's why we're wondering if it's an UE problem rather than a configuration one, or an issue of other code not executing earlier in the line.

Of additional note: their system runs the game from a removeable hard drive. When the hard drive was connected to our system, their copy of the game ran more expediently and the same errors were present. Running their homebrew projects configuration on our system prevented the encounters being picked up across mods, until they were revalidated.

Their save files will not work in our local copy of the game, producing CTD on attempting to load, regardless of what configuration is used. Also, our configuration which works fine on multiple systems, mostly executes but breaks on reinforcement spawns, anything that comes from a hack template, and several mission types that normally work fine (various VIP missions, for example).

Appreciate it's completely out of your wheelhouse, as it is ours. But thanks again, for helping us and future readers resolve dumb problems you didn't even create.

So what you're saying is 'we broke it ourselves, can you help, I guess not then'. Yea sorry I can't offer any help with anything other than this mod's intended setup.

Clarify: They broke it, asked us for help, we came to ask for advice from authors directly so we can better understand and help others in future, and provide illustrative discussion for future readers. We've interjected because of our own interest in the technical side, which occours with this mods intended setup in that environment as well as modified versions.

Offered information to be informative, thorough and accurate.

Thank you for your time and work regardless. Appreciate the support you've offered. Hope to collaborate productively in future again despite this projects shortfalls =)

Distress Beacon has no shortfalls in it's released form, it does exactly what I intended it to do.

Well, since we last spoke, we've resolved the issue on our end (it was effected by an AHW issue). And have made significant strides forwards in diagnosing the issues of other users since then.

Thank you for your time regardless. Feel free to close this as don't believe going in circles will be productive.