Attempting to use "winnowing distillation" as described in the book (where, by the way, it is still called this. It looks like you are making it an overload of Selection Exaltation, now, so that ought to be updated) does not work, nor does there seem to be any other way to order the arguments in a way it will accept.
Expected behavior
if you give it String, num, num, as depicted on the hexbook page, where the numbers are inbounds for the string and represent a substring... give me the substring?
Actual behavior
[12:11:35] [Render thread/INFO]: [CHAT] Selection Exaltation: expected hexcasting.mishap.invalid_value.string at index 2 of the stack, but got 18.00 and it trashes index 2, the string it was looking for… Whoops?
steps to reproduce
get a string from chat with Whisper's. For example the string "0123456789"
Description:
Attempting to use "winnowing distillation" as described in the book (where, by the way, it is still called this. It looks like you are making it an overload of Selection Exaltation, now, so that ought to be updated) does not work, nor does there seem to be any other way to order the arguments in a way it will accept.
Expected behavior
if you give it
String, num, num, as depicted on the hexbook page, where the numbers are inbounds for the string and represent a substring... give me the substring?Actual behavior
[12:11:35] [Render thread/INFO]: [CHAT] Selection Exaltation: expected hexcasting.mishap.invalid_value.string at index 2 of the stack, but got 18.00and it trashes index 2, the string it was looking for… Whoops?steps to reproduce
Additional information
We (Between me, shizurei, and ANN0RAK) also tried rearranging the arguments in reverse, but that just led to the OTHER arg-validation-related bug I reported recently.
Screenshots