JSONPath Experimentation

Experimenting with JSONPath queries using .search

JSONPath expressions can be hard to get right, especially against the deeply nested UAssetAPI JSON structure. The .search command lets you test them interactively before using them in patch files, so you can see exactly what each expression matches.

To help experiment with JSONPath, automod .search can be used on a .sam file consisting of the .uassets of interest and the JSONPath expressions to try against them.

For example:

# EffectTable

$..[?(@.Name == 'N_Drone_Scan')]

$..[?(@.Name == 'N_Drone_Scan')]..[?(@.Name == 'LifeTime')]

$..[?(@.Name == 'LV_Dead_Ocean')]


# TargetFilterTable

drone-scan: $..[?(@.Name =~ /N_Drone_Normal_Scan1_1_Target.*/)]


# DifficultyStatGroupTable

$..Data[16:31]

$..Data[60:86]

That is, the .uasset name should be prefixed with #, with the JSONPath expressions following it in separate lines. The expression can optionally be labeled by prefixing it with (<alphanum>|'_'|'-')+:. Any line that does not adhere to these forms is ignored.

automod-search

The search results are written as JSON files, one file per JSONPath expression, whose name contains the expression’s occurrence number for the .uasset, along with the label, if specified.