Few Tweaks for TFTD Extended

[mark617]

Just a few questions from another post in the OXCE forum they said move here:

1) How can I make it so I continue to get terror (land) missions often? They all but disappear late in the game and I would love to keep these spawning often throughout the campaign. Is there a simple variable change like the "maxRuns: 12" variable re artifact sites (since I want these to continue throughout)?

2) Is it possible to add an execute unconscious mobs function to the melee weapons in-game (vibro lance & thermic lances)? I know some mods had this, and it seems like the addition was problematic based on the following (https://openxcom.org/forum/index.php/topic,3833.45.html).

3) Can I simply adjust the hit chance percentage of melee weapons to a static number, like 90, and simply add the following "skillApplied: false" variable so that the hit percentage would be 90% and not use the hidden melee skill? I assume this would work since it's how the thermal tazers are coded.

Thanks!

[Meridian]

1) remove this line from missionScripts.rul

Code: [Select]

    conditionals: [-1, -2]

2) no, why would I add something I have intentionally removed?

3) yes

[Warboy1982]

just for the record, the melee stat isn't hidden at all in openxcom, it's out there for everyone to see

[mark617]

2) no, why would I add something I have intentionally removed?

I wasn't asking you if you would add it back. I was asking how one could go about adding such a feature.

Your reply in the linked thread only said your implementation of such a feature is "too incompatible with other features," without highlighting said problem(s). You also state people were using it to cheat which, in and of itself, seems irrelevant.

You never mention if it is possible to minimize (or eliminate) the problem(s).

Thus, it seems like this is the place to ask for help re how to add the provided file changes (https://github.com/MeridianOXC/OpenXcom/commit/a936d1c7205cd11dd7c937516b3b9d4580bd0772). Or, even better, finding out if there are similar, but less problematic / more minimal, changes possible.

Thank you 

[Meridian]

I wasn't asking you if you would add it back. I was asking how one could go about adding such a feature.

Ah, sorry, misunderstood the question.

You can add such a feature in just a few simple steps:
1/ fork the openxcom repository on github
2/ download the source code locally
3/ open a c++ IDE of your choice
4/ implement the feature
5/ compile the source code
6/ enjoy

[Nord]

Ah, sorry, misunderstood the question.

You can add such a feature in just a few simple steps:
1/ fork the openxcom repository on github
2/ download the source code locally
3/ open a c++ IDE of your choice
4/ implement the feature
5/ compile the source code
6/ enjoy

KO