Saul J. said: Victor B. said: !cmaster --help is what you use, which works just like token mod. However, help files are still wildly out of date as I continue to add functionality I'm not sure I'm going to support statusinfo import by itself. I'll add it to the list of possible enhancements, but statusinfo hasn't been updated on Roll20 repo in years. Help is on the list until then, post here with questions. Just click around for a bit. A basic configuration is ready out of the gate for D&D 5e. If you are running something else, then it does require a bit more work. Non character linked tokens should be ignored if you are using combat master to roll initiative. However, some people are manually adding non linked tokens into the turnorder and it will generate a failure. It's something I'll need to catch. Until I fix that, link your tokens. No, "!cmaster --help" just puts the info into the chat window. That's extremely difficult to use, especially when trying to configure combat master. I'm talking about having the help in on the same page as where you load scripts into the script library. TokenMod does this as do many other scripts. The tokens ARE linked. I just used a creature from the monster manual compendium. Rolling its initiative from its character sheet, caused the error. All of those tokens are pre-linked. Statusinfo may not have been updated for many years but I, and probably many others, already use it, and already have assigned various symbols to various conditions. Combatmaster should either take that information as input, or not try to re-do it, IMO. Trying to configure many conditions as it's currently implemented in combatmaster is slow, painful, and, frankly, a HUGE turn-off to using combatmaster at all. If you want people to use it, you should make it simple and easy for them. We can continue this is private if you like. I haven't the words for how thoughtless, insensitive, inconsiderate, and downright rude this is. If you want people to use it, you should make it simple and easy for them. @Saul If this is the way you want the program, please write it that way. You're getting something for free and complaining about how the author chooses to do it. It is in it's alpha stages and has taken weeks of work, over a month at least, and has improved every day from just an idea. The author is willing to work with everyone's suggestions - to his credit. Please recognize that he isn't getting paid for this, it's his hobby that he is sharing with everyone else. Kudos should be given, not criticisms and outright rudeness. I think you owe the author an apology, and future consideration on the difference between suggestion and demand. To break down your comment: If you want people to use it - He doesn't want that, he's giving people that option. He's not holding every Roll20 user at gunpoint demanding they install his script and like it. He could just as easily have written it for himself and left it in his computer - never shared. The fact that he has shared it is a gift to the community. Your commentary would make anyone pull their gift back, which I'm glad Victor hasn't. People are using it - I use it in all 3 games I am in on Roll20, and will use it in any future games I am a part of. It's fine however Victor wants it to be, provided it works, and that's as good as we can hope for. you should make it simple and easy for them - he should? Have you set about ChatSetAttr, Powercards, Roll20AM, and Token-Mod? These are what I refer to as power-scripts. They AREN'T easy to use, but once you place a bit of thought into them, they open huge worlds of possibility. The average layman off the street, having no experience with any level of computer programming, would have no idea how to find and adjust attributes with the API, even with the help menus provided. They would first, with great detail, have to be explained what an attribute even is, let alone how to find it (Jacob and TheAaron were very patient with me when I first started in Roll20. VERY PATIENT. Again, Kudos to them, they never HAD to be). Victor has been doing incredible amounts of work to make a functional API, capable of so much to aid in combat flow. And for him, if I may be so bold, I'd say "Sorry, not sorry." in regards to your demands - he's already got enough suggestions on how to improve the script itself keeping him busier than he's got compensation for. And that was just one sentence that upset me, the whole of it sounded the same though. I have spoken all I wish to say on this.