1
OXCE Suggestions DONE / Re: [DONE][Suggestion] A way to display statCaps on the soldier info screen
« on: November 03, 2023, 01:13:23 am »
This new feature is really a good idea 
Welcome, Guest. Please login or register.
Did you miss your activation email? December 05, 2023, 11:35:34 pm
Did you miss your activation email? December 05, 2023, 11:35:34 pm
News: If you can't login, please contact us with your username and e-mail so we can fix it.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
OXCE Suggestions DONE / Re: [DONE][Suggestion] Manual Promotions
« on: November 03, 2023, 01:10:16 am »
Really appreciate this new feature, congrats !
3
OXCE Suggestions NEW / Re: [Suggestion] Soldier Transformation > Add a setting monthlyLimit?
« on: March 12, 2023, 08:27:27 pm »
I made it work
It's not perfect, main inconvenients are:
- the tickets are sent to one Xcom base (Xcom base 1)
- it's a global amount of tickets (I mean, not depending on bases having such a facility)
- the tickets have then to be transferred from base 1 to other bases to be used there
- the transfertime has a minimum of 12 hours (cannot be set to zero or even one hour)
So, finally, I created a ticket for each training type, and will provide 1 ticket per training category each month
It's ok like that, I put this suggestion as solved
Thank you very much for your help, Meridian & Yankee!
And you really do an amazing job here, so many new features and possibilities, QOL, etc.
I love you both as much as I love SupSuper, Warboy & Co
It's not perfect, main inconvenients are:
- the tickets are sent to one Xcom base (Xcom base 1)
- it's a global amount of tickets (I mean, not depending on bases having such a facility)
- the tickets have then to be transferred from base 1 to other bases to be used there
- the transfertime has a minimum of 12 hours (cannot be set to zero or even one hour)
So, finally, I created a ticket for each training type, and will provide 1 ticket per training category each month
It's ok like that, I put this suggestion as solved
Thank you very much for your help, Meridian & Yankee!
And you really do an amazing job here, so many new features and possibilities, QOL, etc.
I love you both as much as I love SupSuper, Warboy & Co 4
OXCE Suggestions NEW / Re: [Suggestion] Soldier Transformation > Add a setting monthlyLimit?
« on: March 12, 2023, 03:10:08 pm »
It works, perfect
I will still make some attempts, then mark this post as solved if I don't find anything else to improve it
Thanks dude !!
I will still make some attempts, then mark this post as solved if I don't find anything else to improve it
Thanks dude !!
5
OXCE Suggestions NEW / Re: [Suggestion] Soldier Transformation > Add a setting monthlyLimit?
« on: March 12, 2023, 02:54:55 pm »
Meridian
Following your advice, I created an event system to trigger expected training tickets ("gym event")
1. An eventScript triggers a monthly event
2. This monthly event provides 5 training tickets
3. Training ticket is declared as an item that will be stored in the database (with no attributes, will see later if needed ; I made tests with some attributes but it does not change the error message)
4. Some extraStrings
Then I added this training ticket as required item in soldierTranformations
Unfortunately, it causes following error message
I tried to change the way to declare requiredItems (with or without brackets, the line after, the line after but with a minus... with same result)
Another question (in case I solve error above): would you have any idea how I could delete each month unused training tickets
Meaning: aim is to allow a "maximum" of 5 training per month but do not store unused training tickets
Example:
Month M: it generates 5 training tickets
Let's assume I train 2 soldiers, so I consume 2 training tickets (and so 3 remaining training tickets)
Month M+1: it generates 5 new training tickets
=> I would like to be able to use only 5 training tickets (and not : 8 training tickets = 5 new TT + 3 old TT)
Thanks in advance for your "science"
Following your advice, I created an event system to trigger expected training tickets ("gym event")
1. An eventScript triggers a monthly event
2. This monthly event provides 5 training tickets
3. Training ticket is declared as an item that will be stored in the database (with no attributes, will see later if needed ; I made tests with some attributes but it does not change the error message)
4. Some extraStrings
Spoiler:
Then I added this training ticket as required item in soldierTranformations
Spoiler:
Unfortunately, it causes following error message
I tried to change the way to declare requiredItems (with or without brackets, the line after, the line after but with a minus... with same result)
Code: [Select]
F:/OXCE/OXCE V7.8 HellMod/user/mods/HellMod/Ruleset/050_Facilities_TagSoldierTransformation.rul: Error for 'STR_TRAINING_SURVIVAL1': wrong node type, expected a map at line 28
(Line 28 is always the line before the one containing requiredItems; in this case, the line 28 is soldierBonusType: STR_SB_TRAINING_SURVIVAL1; if I put requiredItems just after name: STR_TRAINING_SURVIVAL1, the involved line will be the one containing name)Another question (in case I solve error above): would you have any idea how I could delete each month unused training tickets
Meaning: aim is to allow a "maximum" of 5 training per month but do not store unused training tickets
Example:
Month M: it generates 5 training tickets
Let's assume I train 2 soldiers, so I consume 2 training tickets (and so 3 remaining training tickets)
Month M+1: it generates 5 new training tickets
=> I would like to be able to use only 5 training tickets (and not : 8 training tickets = 5 new TT + 3 old TT)
Thanks in advance for your "science"
6
OXCE Suggestions NEW / Re: [Suggestion] Soldier Transformation > Add a setting monthlyLimit?
« on: March 12, 2023, 12:07:09 pm »If you want to limit the number of transformations, you can generate "gym tickets" via geoscape events every month and then use them as resources required for the transformation.
Oh god, Geoscape events, very nice!!
I will try that
You shared an example here
https://openxcom.org/forum/index.php/topic,7215.msg116753.html#msg116753
And the ruleset definition contains lots of very useful information
https://www.ufopaedia.org/index.php/Ruleset_Reference_Nightly_(OpenXcom)#Event_Scripts
Thank you very much
7
OXCE Suggestions NEW / Re: [Suggestion] Soldier Transformation > Add a setting monthlyLimit?
« on: March 11, 2023, 10:59:30 pm »
I use BaseFunc
Let me share an example
And I would like to not allow more than x soldiers per month:
- either globally (as does trainingRooms)
- or per soldierTransformation (throufh a "monthlyLimit")
Let me share an example
Code: [Select]
facilities:
- type: STR_TRAINING_ROOM
spriteShape: 1
spriteFacility: 111
buildCost: 800000
buildTime: 20
monthlyCost: 8000
mapName: XBRO_01
provideBaseFunc: [BASEFUNC_TRAINING]
refundValue: 400000
rightClickActionType: 6
maxAllowedPerBase: 1
soldierTransformation:
- name: STR_TRAINING_SURVIVAL1
listOrder: 100
requires: []
requiresBaseFunc: [BASEFUNC_TRAINING]
keepSoldierArmor: true
allowsLiveSoldiers: true
allowedSoldierTypes: [STR_SOLDIER,STR_VETERAN_SNIPER,STR_VETERAN_GRENADIER,STR_VETERAN_WARRIOR]
requiredPreviousTransformations: []
forbiddenPreviousTransformations: [STR_TRAINING_SURVIVAL1,STR_TRAINING_ENDURANCE1]
cost: 15000
transferTime: 360
includeBonusesForMinStats: true
soldierBonusType: STR_SB_TRAINING_SURVIVAL1
- name: STR_TRAINING_SURVIVAL2
listOrder: 101
requires: []
minRank: 2
requiresBaseFunc: [BASEFUNC_TRAINING]
keepSoldierArmor: true
allowsLiveSoldiers: true
allowedSoldierTypes: [STR_VETERAN_SNIPER,STR_VETERAN_GRENADIER,STR_VETERAN_WARRIOR]
requiredPreviousTransformations: [STR_TRAINING_SURVIVAL1]
forbiddenPreviousTransformations: [STR_TRAINING_SURVIVAL2]
requiredMinStats:
health: 120
reaction: 80
cost: 30000
transferTime: 720
includeBonusesForMinStats: true
soldierBonusType: STR_SB_TRAINING_SURVIVAL2
soldierBonuses:
- name: STR_SB_TRAINING_FIRING1
stats:
firing: 5
- name: STR_SB_TRAINING_FIRING2
stats:
firing: 5
- name: STR_SB_TRAINING_THROWING1
stats:
throwing: 5
- name: STR_SB_TRAINING_THROWING2
stats:
throwing: 5
- name: STR_SB_TRAINING_MELEE1
stats:
throwing: 5
- name: STR_SB_TRAINING_MELEE2
stats:
throwing: 5
- name: STR_SB_TRAINING_SURVIVAL1
stats:
health: 10
reactions: 5
- name: STR_SB_TRAINING_SURVIVAL2
stats:
health: 10
reactions: 5
And I would like to not allow more than x soldiers per month:
- either globally (as does trainingRooms)
- or per soldierTransformation (throufh a "monthlyLimit")
8
OXCE Suggestions NEW / [Solved] Soldier Transformation > Add a setting monthlyLimit?
« on: March 11, 2023, 05:02:38 pm »
Hi,
I had a look at ruleset definition (really great work!) unfortunately I did not find any answer to my need, so I finally decided to ask here
Context: I modded a facility that allows to train soldiers in different manners. I don't want to use standard system that provides a global improvement of soldiers stats, but provides instead some kind of specialization.
Request: I would like to set a monthly limit (i.e., not possible to train more than 5 soldiers per month)
The facility attribute "trainingRooms" doesn't help as it will allow "combat/martial training", that I want to avoid. In fact, I think some kind of "monthlyLimit" per SoldierTransformation should fit this expectation. I know there are already several such attributes for different puposes, as monthlyBuyLimit, etc. (very useful), but I don't know the level of difficulty ot implement it
I don't know if others may be interetested and if it could be considered as interesting/useful by our dear "developpers"
I had a look at ruleset definition (really great work!) unfortunately I did not find any answer to my need, so I finally decided to ask here
Context: I modded a facility that allows to train soldiers in different manners. I don't want to use standard system that provides a global improvement of soldiers stats, but provides instead some kind of specialization.
Request: I would like to set a monthly limit (i.e., not possible to train more than 5 soldiers per month)
The facility attribute "trainingRooms" doesn't help as it will allow "combat/martial training", that I want to avoid. In fact, I think some kind of "monthlyLimit" per SoldierTransformation should fit this expectation. I know there are already several such attributes for different puposes, as monthlyBuyLimit, etc. (very useful), but I don't know the level of difficulty ot implement it
I don't know if others may be interetested and if it could be considered as interesting/useful by our dear "developpers"
9
Open Feedback / Re: Adding atmospheric music
« on: March 10, 2023, 11:42:09 pm »
Thank you for this Yann, I like the first and second songs, I will try to use them
10
OXCE Support / [Answered][Question] Is there a way to "apply" minRank to items/armors
« on: March 03, 2023, 08:21:25 pm »
Hi,
I wonder if there is a possibility to apply some kind of "minRank" to items and armors?
Would be useful for example to make powerful weapons/armors require to be sergent or captain to use/wear it
No idea if it's possible to implement this constraint by script, if some of you have ideas how to deal with that request, I'm clearly interested
I wonder if there is a possibility to apply some kind of "minRank" to items and armors?
Would be useful for example to make powerful weapons/armors require to be sergent or captain to use/wear it
No idea if it's possible to implement this constraint by script, if some of you have ideas how to deal with that request, I'm clearly interested
11
OXCE Suggestions DONE / Re: [DONE] [Suggestion] Soldier bonuses (from transformations and commendations)
« on: February 26, 2023, 08:05:26 pm »
You are right, I will make tests
Thanks for the answers
And congrats for the good job!
Thanks for the answers
And congrats for the good job!
12
OXCE Suggestions DONE / Re: [Documentation] Soldier Transformations
« on: February 26, 2023, 03:19:16 pm »
Perfect, thanks for your answer !
13
OXCE Suggestions DONE / Re: [DONE] [Suggestion] Soldier bonuses (from transformations and commendations)
« on: February 26, 2023, 03:15:00 pm »This is part of oxce already.
Meridian,
I read this full thread, your posts included, but I still would have two question about Commendations and SoldierBonuses
Let's assume I have a commendation as follow:
10 levels of commendation with 4 levels of bonuses:
- Commendation L1 to L4 => SoldierBonus L1
- Commendation L5 to L7 => SoldierBonus L2
- Commendation L8 to L9 => SoldierBonus L3
- Commendation L10 => SoldierBonus L4
Code: [Select]
commendations:
- type: STR_COMMENDATION_ALIENS_KILLED #Total number of kills across a soldier's career that meet the specified criteria
description: STR_COMMENDATION_ALIENS_KILLED_DESCRIPTION
sprite: 1
criteria:
killsWithCriteriaCareer: [10, 20, 30, 40, 50, 75, 100, 200, 300, 500]
soldierBonusTypes: [STR_SB_COMMENDATION_ALIENS_KILLED1, STR_SB_COMMENDATION_ALIENS_KILLED1, STR_SB_COMMENDATION_ALIENS_KILLED1, STR_SB_COMMENDATION_ALIENS_KILLED1, STR_SB_COMMENDATION_ALIENS_KILLED2, STR_SB_COMMENDATION_ALIENS_KILLED2, STR_SB_COMMENDATION_ALIENS_KILLED2, STR_SB_COMMENDATION_ALIENS_KILLED3, STR_SB_COMMENDATION_ALIENS_KILLED3, STR_SB_COMMENDATION_ALIENS_KILLED4]
killCriteria:
-
- [1, ["STATUS_DEAD", "FACTION_HOSTILE"]]
soldierBonuses:
- name: STR_SB_COMMENDATION_ALIENS_KILLED1
stats:
tu: 5
- name: STR_SB_COMMENDATION_ALIENS_KILLED2
stats:
health: 5
- name: STR_SB_COMMENDATION_ALIENS_KILLED3
stats:
tu: 5
- name: STR_SB_COMMENDATION_ALIENS_KILLED4
stats:
health: 5
Questions:
1) Do I need to declare
Code: [Select]
soldierBonusTypes: [STR_SB_COMMENDATION_ALIENS_KILLED1, STR_SB_COMMENDATION_ALIENS_KILLED1, STR_SB_COMMENDATION_ALIENS_KILLED1, STR_SB_COMMENDATION_ALIENS_KILLED1, STR_SB_COMMENDATION_ALIENS_KILLED2, STR_SB_COMMENDATION_ALIENS_KILLED2, STR_SB_COMMENDATION_ALIENS_KILLED2, STR_SB_COMMENDATION_ALIENS_KILLED3, STR_SB_COMMENDATION_ALIENS_KILLED3, STR_SB_COMMENDATION_ALIENS_KILLED4]
or may I perhaps make it shorterCode: [Select]
soldierBonusTypes: [STR_SB_COMMENDATION_ALIENS_KILLED1, , , , STR_SB_COMMENDATION_ALIENS_KILLED2, , , STR_SB_COMMENDATION_ALIENS_KILLED3, , STR_SB_COMMENDATION_ALIENS_KILLED4]
or even another solution ?2) In given example, will the 10th level of Commendation provide cumulative bonus of
- tu +10
- health +10
or only the bonus attached to the 10th level
- health +5
Said differently, if I want a cumulative result, would I have to declare
Code: [Select]
soldierBonuses:
- name: STR_SB_COMMENDATION_ALIENS_KILLED1
stats:
tu: 5
- name: STR_SB_COMMENDATION_ALIENS_KILLED2
stats:
tu: 5
health: 5
- name: STR_SB_COMMENDATION_ALIENS_KILLED3
stats:
tu: 10
health: 5
- name: STR_SB_COMMENDATION_ALIENS_KILLED4
stats:
tu: 10
health: 10
(It may have to do with reset option, but not sure how to make it work properly)
PS: Commendation and SoldierBonuses modding is really great
14
OXCE Suggestions DONE / Re: [EXE] Soldier Transformations
« on: February 25, 2023, 01:10:15 pm »Here's the ruleset documentation for the modders out there, it's also contained as a text file in the mod attached to the post above:Code: [Select]soldierTransformation:
- name: STR_PROJECT_NAME # (REQUIRED) The name of this project listed in the Soldier Transformations screen
listOrder: 100 # The list order of this project, defaults to increasing by 100 for each project in the mod when not defined
requires: # A list of research projects required before this project appears in the list of available transformations, the default empty list means this project is available from the beginning of the game
#- STR_SOME_RESEARCH
requiresBaseFunc: # A list of base functions required at a base in order to do this project, the default empty list means no special facilities are required
#- SOME_BASE_FUNC
producedSoldierType: STR_SOLDIER # The type of soldier produced by this project - any soldier undergoing this transformation will be switched to this type. If left empty, the soldier type does not change.
producedSoldierArmor: STR_NONE_UC # The armor the soldier produced will have when the project finishes, only used when keepSoldierArmor is false. Leaving it empty will give the soldier the armor defined by the type in the soldiers: ruleset.
keepSoldierArmor: false # Default false, this parameter determines whether or not the soldier will keep the armor they're wearing through this transformation
createsClone: false # Default false, this parameter determines whether the selected soldier has the transformation done to them or a new soldier is created that is a copy of the original and the transformation is done to the new soldier.
needsCorpseRecovered: true # Default true, if your project allows dead soldiers, this determines whether or not you needed to have a corpse item available at the end of the battle in which the soldier died. This does not mean you need the corpse item in your stores, just that it would have been recovered if recover: true was set on the item
allowsDeadSoldiers: false # Default false - can dead soldiers undergo this transformation? If so, they are brought back to life at the base you started this project in
allowsLiveSoldiers: false # Default false - can live, non-wounded soldiers undergo this transformation?
allowsWoundedSoldiers: false # Default false - can wounded soldiers undergo this transformation?
allowedSoldierTypes: # (REQUIRED) This list determines which soldier types can undergo this transformation, the default empty list means nobody can have this project done to them.
#- STR_SOLDIER
requiredPreviousTransformations: # A list of transformation projects that must be done to a soldier before they're eligible for this project, the default empty list means no previous projects are required.
#- STR_SOME_TRANSFORMATION
forbiddenPreviousTransformations: # A list of transformation projects that a soldier cannot have undergone in order to be eligible for this project, the default empty list means no previous projects are forbidden
#- STR_SOME_OTHER_TRANSFORMATION
requiredMinStats: # The minimum stats a soldier must have in order to be eligible for this project, defaults to all 0 so any soldier is eligible
tu: 0
stamina: 0
health: 0
bravery: 0
reactions: 0
firing: 0
throwing: 0
strength: 0
psiStrength: 0
psiSkill: 0
melee: 0
requiredItems: # A list of items that must be consumed from the base's stores in which you start this project, the default empty list means no items are used
#STR_SOME_ITEM: 1
cost: 50000 # The cost of the project in dollars
transferTime: 0 # Soldiers can be put in a transfer back to the base where they started if this parameter is greater than the default of 0 hours. New clones or resurrected soldiers are automatically given a transfer to the base with a default of 24 hours.
recoveryTime: 0 # The amount of wound recovery time a soldier is given after this project completes and the transfer, if any, is completed. The default value is 0 days.
flatOverallStatChange: # A direct change to the soldier's overall stats when undergoing this project, can be positive or negative - tu: 5 means the soldier will gain 5 max time units, while tu: -5 means the soldier will lose 5 max time units. The default of 0 means no change.
tu: 0
stamina: 0
health: 0
bravery: 0
reactions: 0
firing: 0
throwing: 0
strength: 0
psiStrength: 0
psiSkill: 0
melee: 0
percentOverallStatChange: # A percent change to the soldier's overall stats when undergoing this project, can be positive or negative - tu: 5 means the soldier will gain an extra 5% of their max time units, while tu: -5 means the soldier will lose 5% of their max time units. The default of 0 means no change.
tu: 0
stamina: 0
health: 0
bravery: 0
reactions: 0
firing: 0
throwing: 0
strength: 0
psiStrength: 0
psiSkill: 0
melee: 0
percentGainedStatChange: # A percent change to the soldier's stats, but instead of taking a portion of the overall stats, this only applies to the stats they've trained up from their initial values, can be positive or negative - firing: -100 means the soldier will lose all of the firing accuracy they trained since joining, while firing: 10 means they gain 10% of the amount they trained over their initial values. The default of 0 means no change.
tu: 0
stamina: 0
health: 0
bravery: 0
reactions: 0
firing: 0
throwing: 0
strength: 0
psiStrength: 0
psiSkill: 0
melee: 0
useRandomStats: false # Default false, when true, this parameter overrides the stat changes above and has the produced soldier roll random stats according to their new soldier type from this transformation project.
lowerBoundAtMinStats: true # Default true, this parameter determines whether or not any changes in stats from this project should go below the minStats defined on the new soldier type.
upperBoundAtMaxStats: false # Default false, this parameter determines whether or not any changes in stats from this project should go above the maxStats defined on the new soldier type.
upperBoundAtStatCaps: false # Default false, this parameter determines whether or not any changes in stats from this project should go above the statCaps defined on the new soldier type.
The associated strings are:Code: [Select]extraStrings:
- type: en-US
strings:
#SoldierTransformationAssignState.cpp
STR_TRANSFER_TIME: "Transfer Time>{ALT}{0}"
STR_RECOVERY_TIME: "Recovery Time>{ALT}{0}"
STR_CURRENT_STATS: "Current stats"
STR_CHANGES: "Changes"
Explanation are really great !!
Providing new features is wonderful, explaining how to implement, with so much details, is paradise
15
OXCE Suggestions DONE / Re: [Documentation] Soldier Transformations
« on: February 25, 2023, 01:06:30 pm »
Hi,
I'm really interested by this amazing feature (once more ), but I fail to download zip file attached in first post
May it be this zip archive is corrupted?
EDIT: not sure if zip contains interesting resources or if it has only to do with programming, anyway I succeeded to mod it, very good feature
I'm really interested by this amazing feature
(once more ), but I fail to download zip file attached in first postMay it be this zip archive is corrupted?
EDIT: not sure if zip contains interesting resources or if it has only to do with programming, anyway I succeeded to mod it, very good feature