[[1d100cs>-1]] (or any negative number, any dice roll) will always return 1 and cause target macros to fail. Not sure what update broke this but we just discovered it recently. This happens from macros, our custom sheet, chat and api. Not a real big issue I know but my game has been using these types of rolls to highlight success based on a lot of variable modifiers that can sometimes lead to a negative cs. In practice the roll goes something like [[1d100cs<[[ [[@{selected|condition}]] + ?{Mod|0} ]] which certain very bad situations leads to rolls that equate to 1d100cs<-10. When inline rolls first came out, it would work just fine. Previously 1d100cs<-10 would roll 1d100 and always be unhighlighted. Now it always rolls 1 with no highlight. We use this type of roll for its concise formatting (for use in powercards and macros) and because the value matters in addition to being a success or fail. It's not game breaking for us since if the macro fails to fire off we know there was a negative chance at success and just call it a fail and move on.
