Editing Enemy Parameters
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 3: | Line 3: | ||
Enemy behaviour parameters are configured in each enemy's blueprint file, or sometimes its superclass file. These exist in <code>Carrot4/Placeables/Teki</code> and <code>Carrot4/Placeables/Teki/Base</code> for superclasses and can be edited as JSON, once decoded. For enemy parameters relating to economy/health/carrying/damage see [[Data Table/Actor Parameters]]. | Enemy behaviour parameters are configured in each enemy's blueprint file, or sometimes its superclass file. These exist in <code>Carrot4/Placeables/Teki</code> and <code>Carrot4/Placeables/Teki/Base</code> for superclasses and can be edited as JSON, once decoded. For enemy parameters relating to economy/health/carrying/damage see [[Data Table/Actor Parameters]]. | ||
| − | While the blueprint files are quite large, they are mostly full of irrelevant code for the common user. The file is split into "generator variables" which are used to set the base characteristics of an enemy at runtime, likely laid underneath an enemy's instance-parameters, which come from [[ | + | While the blueprint files are quite large, they are mostly full of irrelevant code for the common user. The file is split into "generator variables" which are used to set the base characteristics of an enemy at runtime, likely laid underneath an enemy's instance-parameters, which come from [[https://pikmintkb.com/wiki/ActorSerializeParameter_and_AI]]. |
The gen variables one is likely looking for are: | The gen variables one is likely looking for are: | ||
