Jump to content

Ambigious Terms


pasmon79

Recommended Posts

It is simply a variable, a counter, for how dangerous the area near the base has become. It is used for things like which advice is given (such as we need to build more outposts), the maximum allowed infestations, whether certain fatecards are allowed, and some events. A lower value is safer, higher represents a more dangerous situation, and it increases over time on a given level.

 

It is mainly set by events in enclaves.xml, such as <RTSStat_Set DurationCancellable="" OutputAmount="40" OutputDuration="" OutputId="Status.Enemy.ChallengeLevel" PauseWhenOffline="" />

 

and then referenced in other files, such as <Check InputAmount="40" InputFlags="" InputId="Status.Enemy.ChallengeLevel" />

 

Look them up as partials, ie. instead of Status.Enemy.ChallengeLevel, search for ChallengeLevel, and you will find them in globalconstants.xml usually.

Edited by qmjs
Link to comment
Share on other sites

Just because they look alike doesn't mean that they are related.

 

Game.Player.DangerLevel is one value. <Group Name="Game"><Subgroup Name="Player"><Value Default="0" Name="DangerLevel">
DangerLevel is an enclave value. <EnclaveValues><Value Default="0" Name="DangerLevel">
DangerLevel is also a scene value. <Group Name="Scene"><Subgroup Name="DangerLevel">

 

 

 

<Value>Manual.DangerLevel</Value> will always be 0 as the variable is not defined. The scenes in which it is referred to do not ever actually play. There are many that are unused in the game.

 

The ChallengeLevel in rtsdata is the default 0 for a variable definition. It is never used at that value in Breakdown.

Edited by qmjs
Link to comment
Share on other sites

The game assign "ChallengeLevel" during gameplay once in each instance of home-enclave as given below.

<RTSStat_Set DurationCancellable="" OutputAmount="40" OutputDuration="" OutputId="Status.Enemy.ChallengeLevel" PauseWhenOffline="" />

Why does it need to do each time after the transition in enclave? Does the value in ChallengeLevel drops to zero at some instance?

Link to comment
Share on other sites

Did you look at the action name that it occurs in? That is a clue to why some values are set multiple times.

 

It is essentially making sure that the variables have a valid value at each stage.

Edited by qmjs
Link to comment
Share on other sites

Okay i got it.

 

There are some ActionID defined in both "rtsevents, mission and enclaves" like "AwayMission" and some are defined in one place only like for setting "Challenge Level" and possibly linked with some compiled file.

 

Can we create an ActionID of our own while creating a new mission?

Edited by pasmon79
Link to comment
Share on other sites

ActionID is just a name. As long as it is unique within the active section, it can be anything. They are named what they are so the programmers can locate them when working with multiple files, which is why they are named according to what they do.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...