T
@vinicity
it's not meant to be a string intentionally. it can be, but in reality can and should be anything you throw in there. as an example if you wanted to see the location of a sprite as an example you should actually plop in setBreakpoint(1, "some id value", getSpriteLocation(nameOfSprite)) and it will display the resulting vector. again, the idea was to keep it flexible so you could display custom messages, arrays, values, function results, etc. to pinpoint what something is doing or its value at any given time.
as far as the text goes, yea there were a handful of compromises i had to make to keep it compact but also retain the complete functionality needed to be useful. hopefully something like this will actually make it into the editor itself so we don't need this.
