Messages

16

Work In Progress / Re: Soldier Statstrings - Any way to get the numeric value? (SOLVED - Inelegantly)

« on: August 04, 2017, 05:43:24 pm »

Yeah it was just copying and replacing blocks of text, luckily Notepad++ allows to replace all in a selected block so I just had to change one number each block.

I like the idea of truncating after 199, thanks, one of the mods is already in the 100's but its just a new start so I don't know yet how high it goes, I'll check those rulsets.

17

Work In Progress / Re: Soldier Statstrings - Any way to get the numeric value? (SOLVED - Inelegantly)

« on: August 04, 2017, 03:28:11 pm »

Thanks for the info, as soon as I finish the code I'll definitely move it to a mod.

As far as the custom stats, its just a personal desire to finally switch from /10 to the actual stat, since the UFOpaedia examples already had a Template for it, I just had to convert that into OpenXcom code.

It's all working so far up to 99, I just need to tweak the 100's.

I'm trying several mods that appear to offer more than 100 max in stats:

Final Mod Pack
SoldiersExtendedXCOM1
Soldier Specialization

One or more of those may be redundant as far as higher Soldier Stats.  What is the highest level of Soldier Stats you have seen in mods that you have tried?

18

Work In Progress / Re: Soldier Statstrings - Any way to get the numeric value? (SOLVED - Inelegantly)

« on: August 04, 2017, 07:10:07 am »

OPENXCOM does open old Geoscape saves of the original game and seems to transfer soldier stats unless I'm missing something.

This is for starting a new game for a new install for my grandson.

When I turn on Statstrings for a new install, it is going to use the Standard copy of C:\Program Files (x86)\OpenXcom\standard\XcomUtil_Statstrings.rul, is what I thought it would do.

Meaning if I want my old custom statstrings I have to modify inside the OpenXCOM .rul format?

Are you saying that if i copy an old DOSBox save game and open it in OPENXcom, it will rewrite the XcomUtil_Statstrings.rul to match those saved statstrings?  Or is it just going to ignore the saved statstrings after the name (which in the case of my saved game has only Rank Abbreviation from Xcomutil and the custom statstrings, I erase the names when starting on DOSBox XCOM).

My old version of Xcomutil custom statstrings used the '#' code so it was always only a single number (total/10).  But the UFOpaedia entry for statstrings doesn't even mention the '#' code.

So I decided to see if I could use OpenXcom statstrings format to get the actual full stat number.  I was hoping there was maybe a more succinct option or a function that I hadn't found already to write this into XcomUtil_Statstrings.rul.

Did I make that understandable or just more confusing, sorry, I am just a plinker and not a coder at all.

19

Work In Progress / Soldier Statstrings - Any way to get the numeric value? (SOLVED - Inelegantly)

« on: August 03, 2017, 11:31:27 pm »

(SOLVED with some experimentation)

Here's the final code for any particular stat, 0-99.  With even 2 digit full numbers you will be limited to about 7 stats on any screen and that completely removes any Soldier Name and limits you to single letter Stat ID letter. Without a way to auto change/populate the ruleset, I don't see this as worthy of publishing as a full mod.

Code: [Select]

# TIME UNITS 10's 
  - string: "T"
    tu: [0, ~]
  - string: "1"
    tu: [10, 19]
  - string: "2"
    tu: [20, 29]
  - string: "3"
    tu: [30, 39]
  - string: "4"
    tu: [40, 49]
  - string: "5"
    tu: [50, 59]
  - string: "6"
    tu: [60, 69]
  - string: "7"
    tu: [70, 79]
  - string: "8"
    tu: [80, 89]
  - string: "9"
    tu: [90, 99]
   
# TIME UNITS Ones

  - string: "0"
    tu: [10, 10]
  - string: "1"
    tu: [11, 11]
  - string: "2"
    tu: [12, 12]
  - string: "3"
    tu: [13, 13]
  - string: "4"
    tu: [14, 14]
  - string: "5"
    tu: [15, 15]
  - string: "6"
    tu: [16, 16]
  - string: "7"
    tu: [17, 17]
  - string: "8"
    tu: [18, 18]
  - string: "9"
    tu: [19, 19]
   
  - string: "0"
    tu: [20, 20]
  - string: "1"
    tu: [21, 21]
  - string: "2"
    tu: [22, 22]
  - string: "3"
    tu: [23, 23]
  - string: "4"
    tu: [24, 24]
  - string: "5"
    tu: [25, 25]
  - string: "6"
    tu: [26, 26]
  - string: "7"
    tu: [27, 27]
  - string: "8"
    tu: [28, 28]
  - string: "9"
    tu: [29, 29]
   
  - string: "0"
    tu: [30, 30]
  - string: "1"
    tu: [31, 31]
  - string: "2"
    tu: [32, 32]
  - string: "3"
    tu: [33, 33]
  - string: "4"
    tu: [34, 34]
  - string: "5"
    tu: [35, 35]
  - string: "6"
    tu: [36, 36]
  - string: "7"
    tu: [37, 37]
  - string: "8"
    tu: [38, 38]
  - string: "9"
    tu: [39, 39]

  - string: "0"
    tu: [40, 40]
  - string: "1"
    tu: [41, 41]
  - string: "2"
    tu: [42, 42]
  - string: "3"
    tu: [43, 43]
  - string: "4"
    tu: [44, 44]
  - string: "5"
    tu: [45, 45]
  - string: "6"
    tu: [46, 46]
  - string: "7"
    tu: [47, 47]
  - string: "8"
    tu: [48, 48]
  - string: "9"
    tu: [49, 49]

  - string: "0"
    tu: [50, 50]
  - string: "1"
    tu: [51, 51]
  - string: "2"
    tu: [52, 52]
  - string: "3"
    tu: [53, 53]
  - string: "4"
    tu: [54, 54]
  - string: "5"
    tu: [55, 55]
  - string: "6"
    tu: [56, 56]
  - string: "7"
    tu: [57, 57]
  - string: "8"
    tu: [58, 58]
  - string: "9"
    tu: [59, 59]
   
  - string: "0"
    tu: [60, 60]
  - string: "1"
    tu: [61, 61]
  - string: "2"
    tu: [62, 62]
  - string: "3"
    tu: [63, 63]
  - string: "4"
    tu: [64, 64]
  - string: "5"
    tu: [65, 65]
  - string: "6"
    tu: [66, 66]
  - string: "7"
    tu: [67, 67]
  - string: "8"
    tu: [68, 68]
  - string: "9"
    tu: [69, 69]
   
  - string: "0"
    tu: [70, 70]
  - string: "1"
    tu: [71, 71]
  - string: "2"
    tu: [72, 72]
  - string: "3"
    tu: [73, 73]
  - string: "4"
    tu: [74, 74]
  - string: "5"
    tu: [75, 75]
  - string: "6"
    tu: [76, 76]
  - string: "7"
    tu: [77, 77]
  - string: "8"
    tu: [78, 78]
  - string: "9"
    tu: [79, 79]

  - string: "0"
    tu: [80, 80]
  - string: "1"
    tu: [81, 81]
  - string: "2"
    tu: [82, 82]
  - string: "3"
    tu: [83, 83]
  - string: "4"
    tu: [84, 84]
  - string: "5"
    tu: [85, 85]
  - string: "6"
    tu: [86, 86]
  - string: "7"
    tu: [87, 87]
  - string: "8"
    tu: [88, 88]
  - string: "9"
    tu: [89, 89]

  - string: "0"
    tu: [90, 90]
  - string: "1"
    tu: [91, 91]
  - string: "2"
    tu: [92, 92]
  - string: "3"
    tu: [93, 93]
  - string: "4"
    tu: [94, 94]
  - string: "5"
    tu: [95, 95]
  - string: "6"
    tu: [96, 96]
  - string: "7"
    tu: [97, 97]
  - string: "8"
    tu: [98, 98]
  - string: "9"
    tu: [99, 99]



==================

Started trying my hunch below and I have it working for 50-59, just need to do all the typing unless someone has a more elegant solution:

Code: [Select]

statStrings:
# 10's 
  - string: "T"
    tu: [0, ~]
  - string: "1"
    tu: [10, 19]
  - string: "2"
    tu: [20, 29]
  - string: "3"
    tu: [30, 39]
  - string: "4"
    tu: [40, 49]
  - string: "5"
    tu: [50, 59]
  - string: "6"
    tu: [60, 69]
  - string: "7"
    tu: [70, 79]
  - string: "8"
    tu: [80, 89]
  - string: "9"
    tu: [90, 99]
  - string: "10"
    tu: [100, ~]
# Ones   
  - string: "0"
    tu: [50, 50]
  - string: "1"
    tu: [51, 51]
  - string: "2"
    tu: [52, 52]
  - string: "3"
    tu: [53, 53]
  - string: "4"
    tu: [54, 54]
  - string: "5"
    tu: [55, 55]
  - string: "6"
    tu: [56, 56]
  - string: "7"
    tu: [57, 57]
  - string: "8"
    tu: [58, 58]
  - string: "9"
    tu: [59, 59]

------------------------

Hello All,

I have searched the forum and also the wiki for examples of StatStrings in order to attempt to use my original setup from my DOSbox install of UFO: Enemy Unknown/UFO Defence

I see how the OpenXCOM current ruleset is arranged but I don't see how I can get what I would like without several pages of entries.

Here is what I use in DOSbox with orig XCOMUtil.cfg  It gives a prefix and then the numeric number (total Value divided by 10 per XCOMutil) for namestat: /T7B5s5F5r5P1p8

T t:0-255
# t
B b:0-255
# b
s s:0-255
# s
F f:0-255
# f
r r:0-255
# r
P k:0-255
# k
p q:0-255
# q

An example at UFOpaedia shows this using orig XCOMUtil w/o the '#' character but I'm not sure how it would be translated to OpenXCOM code w/o several nested/consecutive blocks for each soldier stat.

2 s:20-29
3 s:30-39
4 s:40-49
5 s:50-59
6 s:60-69
7 s:70-71

0 s:20-20
1 s:21-21
2 s:22-22
3 s:23-23
4 s:24-24
5 s:25-25
6 s:26-26
7 s:27-27
8 s:28-28
9 s:29-29.....


Since I can't see if the "#" symbol is active in the current code, I found this that looks like something close but I think this would take several different blocks to work and I don't know if they would work together if at all.  And it is still ranges and not the single number.  I guess I could just make all the extra lines for smaller ranges if that would work?  Or could I copy the example above into the same layout for individual digits.

 - string: "a"
   firing: [0, ~]
 - string: "0"
   firing: [0, 49]
 - string: "1"
   firing: [50, 57]
 - string: "2"
   firing: [58, 65]
 - string: "3"
   firing: [66, 73]
 - string: "4"
   firing: [74, 81]
 - string: "5"
   firing: [82, 89]
 - string: "6"
   firing: [90, 97]
 - string: "7"
   firing: [98, 105]
 - string: "8"

Using these two above, is this the format that is needed?

 - string: "T"
   tu: [0, ~]
 - string: "1"
   tu: [10, 19]
 - string: "2"
   tu: [20, 29]
 - string: "3"
   tu: [30, 39]
 - string: "4"
   tu: [40, 49]
 - string: "5"
   tu: [50, 59]
 - string: "6"
   tu: [60, 69]
 - string: "7"
   tu: [70, 79]
 - string: "8"
   tu: [80, 89].......

Followed by:

- string: "0"
   tu: [10, 10]
 - string: "1"
   tu: [11, 11]
 - string: "2"
   tu: [12, 12]
 - string: "3"
   tu: [13, 13]
 - string: "4"
   tu: [14, 14]
 - string: "5"
   tu: [15, 15]
 - string: "6"
   tu: [16, 16]
 - string: "7"
   tu: [17, 17]


Would that pattern work for each STAT ?  Do I have to list the individual numbers nested within the "tens" instead of after?
 

I may just not be seeing the simple solution to this and would appreciate any help.

Thanks