Gauss said: You have an extra pair of "{" "}" brackets around your query, that is what is causing the problem. Remove them, it will work correctly. No, because /r {?{1. Keep|1}} + 3d6sdkh3 or /r { ?{1. Keep|1} + 3d6sd}kh3 both keep the highest 3 of the 3 d6 (pointless) and then adds the prompt input. This is not the same, and exactly how I stumbled into this. However, expanding the 2d6 each into their own group would work: /r { {?{1. Keep|1}} , {?{2. Keep|1}} , {1d6}, {1d6} }kh3 but this has the problem that the const values have no highlighting of what was kept (even if it is calculated correctly). What works with the highlighting is: /r { ?{1. Keep|1} * 1d1 , ?{2. Keep|1} * 1d1 , 1d6 , 1d6 }kh3 but this produces incredibly ugly and hard to read results, and converting the results of the multiplication back to to inline rolls, again converts them to "m"-typed rolls, which the engine does not allow. In any case I have not found out how to do sorting, and if it is even possible (or at least I would not know how to apply "sd" to a grouped roll). Note: The extract curly brackets are required to convert M-rolls to regular results before being mixable, at least I think so. Another to me really mysterious result is: /r [[{ [[?{1. Keep|1} * 1d1cs6cf0]] , [[?{2. Keep|1} * 1d1cs7cf0]], [[1d6cs6cf0]] , [[1d6cs7cf0]] }kh3]] I have absolutely no idea how the result is 17. I would have expected 6+6+4=16. message Id: "-NPDLbrc1DKQnv5Nozj3"