This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
developer_integration [2019/11/08 20:35] – created b0ardface | developer_integration [2023/12/26 20:45] (current) – external edit A User Not Logged in | ||
---|---|---|---|
Line 16: | Line 16: | ||
* '' | * '' | ||
* '' | * '' | ||
+ | * '' | ||
* '' | * '' | ||
Line 103: | Line 104: | ||
| 0x0059 | Rydia' | | 0x0059 | Rydia' | ||
| 0x005A | Fallen Golbez (vanilla Crystal location) | | | 0x005A | Fallen Golbez (vanilla Crystal location) | | ||
- | | 0x005B | + | | 0x005D |
===== MSU-1 Support ===== | ===== MSU-1 Support ===== | ||
Line 194: | Line 194: | ||
/ | / | ||
- | Along with these additional parameters in the query string or POST data: | + | The body of this request should be a JSON object |
- | flags : the desired flag string | + | following format: |
- | seed : the randomization | + | |
+ | | ||
+ | "flags" | ||
+ | " | ||
+ | " | ||
+ | } | ||
+ | |||
+ | 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: | ||
+ | |||
+ | { | ||
+ | " | ||
+ | } | ||
- | This will return a JSON response in one of the following formats: | + | 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 |