[Script] ScriptCards - Thread #2

ScriptCards cannot currently delete an object. I have a small script I wrote that I call from some of my summoning ScriptCards that can deleted tokens to overcome the no delete shortcoming. I can post it if it is helpful but you will need something in addition to ScriptCards if you want to delete objects.

The inability to delete objects via ScriptCards was an intentional limitation to prevent people from creating malicious scripts. It isn't difficult to add that ability, but I'd make it configurable to allow the game owner to restrict it to GMs or something similar.

Keep higher one just returns zero. What am I doing wrong here? --=Skill|{@{selected|Grapple},@{selected|DX},@{selected|PunchSkill}}kh1 Edit: Newer mind, fixed it --=Skill|[[{@{selected|Grapple},@{selected|DX},@{selected|PunchSkill}}kh1]]

ScriptCards 3.0.14 headed to OneClick The latest version of ScriptCards is just about to go live on OneClick. Besides a couple of bug fixes, this version adds: - Support for setting bar4 values "intelligently" (like linking, etc. You could already set them individually) - Support for triggers for change:pin add:pin and destroy:pin Map pins are already manipulatable in ScriptCards via --! using the "pin" object type, so no changes were needed to support them. The OneClick change was merged on he back end today so it should be active in a day or so.

ScriptCards 3.0.16 headed to OneClick, 3.0.17 on GitHub Fast on the heels of 3.0.14, 3.0.16 is now on OneClick. Besides some internal cleanup and prep work for new features, there is only one major change: - Added the buttonwidth setting, which defaults to "auto". This setting is a per-line setting that can be set to a css size indicator (ie, 20%, or 50px, or 60em, etc.) and will update the style output for subsequent buttons using that width. Currently on the GitHub version, I've added a feature I'm calling "pointers" (maybe not the best name...) that allows you to store object properties on the Java side so they don't get mangled by running them through the ScriptCards text processor. Useful, for example, for transferring things like the Action property of a character ability that might contain script code.