2 réponses à ce sujet

[FergusM]

When my level loads up, the PC is level one. The row for the area in areadata.xls has 1 as the min level, and 1 as the max, so by default everything should just scale to level 1. However, there is an enemy that I wish to make level 7. As such, I put 7 as both his min and max level in the .utc file. However, he remains level 1 in game. How do I get the scaling system to use the .utc values? Even deleting the row in areadata.xls did not help, they still went to level 1. If I change the minlevel in areadata to 7, then everyone is level 7.



It might be worth noting that whenever I export anything I get the error message "Some resources have failed their post-processing..." with the specific error "Could not find the variable 2da "var_mymodule"," that being the module variable 2da I am using. However, it still successfully reports each file exporting, and in fact the changes from these exports are visible in game; I can make my enemy into a giant spider, just not level 7. Even scripts which pull variables from that 2da still work. I think this might be irrelevant, but who knows.

[Challseus]

As far as I know, those min/max attributes in the creature editor don't work. I've been actually using a variable from var_creature, MIN_LEVEL. In fact, I haven't messed with adding any of my areas to that 2DA. I just want more control over the levels of certain creatures.

So, perhaps this could be a work around for you.

EDIT - Just took a look at the function, AS_GetCreatureLevelToScale() from the script, sys_autoscale_h.nss. Those min/max attributes definitely aren't used, so I would just stick with using the variable, which is clearly used.

Modifié par Challseus, 17 février 2010 - 01:48 .

[FergusM]

Yeah, I was hesitant to say they were totally broken but I certainly couldn't get them to have any effect. I'll just use the variables, that's an easy enough alternative.