Modding Help Treasure Pool Question

When looking at treasure pools, what are the numbers before each array ( i think thats what they are called).

Example - What do the 0 and 3.9 represent? Are those the weights? If so, it seems weird having something odd like 3.9 instead of just making it 4. Is there a reason for that?

Code:

"stim" : [
    [0, {
      "pool" : [
        {"weight" : 0.25, "item" : [ "redstim", 2]},
        {"weight" : 0.25, "item" : [ "bluestim", 2]},
        {"weight" : 0.25, "item" : [ "greenstim", 2]},
        {"weight" : 0.25, "item" : [ "yellowstim", 2]}
      ]
    }],
    [3.9, {
      "pool" : [
        {"weight" : 0.25, "item" : [ "redstim", 3]},
        {"weight" : 0.25, "item" : [ "bluestim", 3]},
        {"weight" : 0.25, "item" : [ "greenstim", 3]},
        {"weight" : 0.25, "item" : [ "yellowstim", 3]}
      ]
    }]
  ],

 

I believe that's a threat level minimum. Although I have no idea why it would use 3.9 instead of all integers.

But if you look at the tenant pool, that's what it looks like to me.

 

Can confirm @bk3k, that's threat level minimum loot acquisition.

Level 0 loot can be accessed at any tier, anything that follows up threat level 0 will be replaced by the highest level the environment is in. Example, you can have a 0, 3.9, and 5.9 threat level loot configurations: any planet below threat level 5 will spawn the lv3.9 configuration, while any planet below threat level 2 will spawn the lv0 configuration.

 

On the whole non-integer thing on the threat level, I think it's processed as "greater than" and not "greater than or equal to". So, setting it to 4 would end up EXCLUDING threat level 4.

If anyone knows for sure otherwise, please correct me.

 

Quite an interesting theory @GreenWiz! Decided to try it out myself.

So here's a little sample I came up with: nothing too crazy, just a pool with various levels.

Code:

"gyrPoolTest" : [
    [0, {
        "fill" : [
            { "item" : [ "orangestim", 1 ] }
        ]
        } 
     ],
    [1, {
        "fill" : [
            { "item" : [ "redstim", 1 ] }
        ]
        } 
     ],
    [2, {
        "fill" : [
            { "item" : [ "bluestim", 1 ] }
        ]
        } 
     ],
    [3, {
        "fill" : [

            { "item" : [ "yellowstim", 1 ] }
        ]
        } 
     ],
    [4, {
        "fill" : [
            { "item" : [ "greenstim", 1 ] }
        ]
        } 
     ]
    ]

So, I've attempted this test with both integer and non-integer numbers. On both occasions, upon using "/spawntreasure gyrPoolTest [level]", whichever level I had input would spawn the tier before it: say, if I had put 4, mimicking a threat-level 4 planets, it would spawn the lv3 treasure. This works either if you use an integer or a non-integer, so I don't exactly know why the x.9 may be necessary; and as an additional note, trying to input a decimal level in the spawntreasure command just errors you out, further implying that perhaps the decimal is just entirely useless.

So the tables work the same disregarding if they have the decimal tacked on or not... I don't think the game might care, honestly.

 

with a tier 4 planet spawning tier 3 treasure, 0=t1, 1=t2, 2=t3, 3=t4, 4=t5, etc

 

That's what I gathered as well: it makes some sense given that most tables start with 0 rather than 1, so while it may not be exactly what's happening there, it seems like a good theory to keep in mind!