This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
developer_integration [2020/01/03 19:23] – [In-game Tracking] b0ardface | developer_integration [2022/03/07 00:03] – [In-game Tracking] added objective tracking info wylem | ||
---|---|---|---|
Line 16: | Line 16: | ||
* '' | * '' | ||
* '' | * '' | ||
+ | * '' | ||
* '' | * '' | ||
Line 193: | Line 194: | ||
/ | / | ||
- | Along with these additional parameters in the query string or POST data: | + | The body of this request should be a JSON object |
- | | + | following format: |
- | seed : the randomization seed (optional) | + | |
- | This will return a JSON response in one of the following formats: | + | { |
+ | " | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | |||
+ | NOTE: For backwards compatibility, | ||
+ | passed as URL query parameters or formdata values in the body instead. | ||
+ | To use metaconfigurations, | ||
+ | |||
+ | The metaconfiguration object, and all fields within it, are optional. | ||
+ | Note that when a metaconfiguration is specified, a " | ||
+ | generated -- rerunning the same generation parameters later will | ||
+ | result in a different seed. | ||
+ | |||
+ | The metaconfig object has this format: | ||
+ | |||
+ | { | ||
+ | " | ||
+ | } | ||
+ | |||
+ | The generate call will return a JSON response in one of the following | ||
+ | formats: | ||
// If the generation process started correctly | // If the generation process started correctly |