RPTools.net

OMGIzAToken wrote:That's a pretty cool idea too (and fast) but I'd hate to be the players with a low initiative mod.

Also why does everyone have "dragon" or "Great Wyrm" written under their name and I have to be a freaking Kobold...it's not fair I tellz ya!

Eat yer vitamins.

Sepp wrote:Gah... I needed single quotes...
*feels stupid*

Bah, don't stress over it. Quotes bite everyone now and then.

swings his axe against <span style="color:red">One creature</span> for <!-- {roll=1d20} --> <span style="color:red">{roll+WeaponCBonus+StrBonus+LevelBonus+MiscAttBonus }</span> vs AC <span style="color:red">{if(roll>=20," Critical Hit! ",if(roll<=1," Cri...

For all of the programmers in this crazy group. Is there any current languages that are case sensitive? I can not think of any. Honestly, I can't think of any. Insensitivity helps avoid X=foo x=bar X^2 = x * x = program comes to a grinding halt and the machinery begins eating people. [sigh]Why am I...

trevor wrote:Oh yeah, and the init panel should _only_ work with tokens, nothing on any other layer, cause that would be silly

But, but, what about the Candle Stick of Death?

I appreciate that is a work around, but the necessity to create a macro button for each character is going to result in a LOT of extra macros... :/ If you don't mind a two-step solution, here's a technique that will work. Define a campaign property called ChatColor. Set it on each token you want to...

I believe === is already an operator in use in php or javascript. Yes. That's why I said "I like Orchard's idea of === as that's how JavaScript works". Whereas with a case mismatch problem, the macro will ask for a value for the undefined property/variable. I was talking about case sensit...

I am neutral on whether the PCs can see the NPCs and all the variations of that. Excellent, then you won't mind if I say "DON'T LISTEN TO BRAD, unless you're watching his videos and then you MUST listen to him! " ;) Personally, if I have a critter running around in the shadows that the PC...

Could you set a way so that when I do an impersonate, the font style and color change happen automatically? I feel reasonably confident in my ability to forget to type the /cc every time, especially when I'm in a hurry. Me too...what I have done previously is just make a global macro button for eac...

trevor wrote:

Naryt wrote: If the plan is to make property name comparisons case insensitive as well

That's the plan.

As long as it's consistent then I vote for whatever happens.

so, I'm still not hearing a case for A != a other than "it makes me feel creepy" :) Is there a case where it will matter ? I'm even dubious if there will be a case where people will even notice. My concern now is that if we move away from A != a then new users are going to want token prop...

so, I'm still not hearing a case for A != a other than "it makes me feel creepy" :) Is there a case where it will matter ? I'm even dubious if there will be a case where people will even notice. My concern now is that if we move away from A != a then new users are going to want token prop...

Being the one that actually wrote the /cc command, let me see if I can drum up something similar for font face.

UPDATE
OK, life is going to be a bit complicated for the next couple of days but I should be able to put a patch together that will allow for font changes by the weekend.

I just have to say... why would this be any different than misstyping [strength] instead of [Strength] and being prompted for the value of strength since it's not a defined property and Strength is. Excellent point and for consistency's sake I would suggest that we keep that throughout the program....

I agree with BigO here: I would have coded it the way it is, and like trevor the precision of the current method appeals to me. This is despite the fact that I am not a programmer. I am a psychologist, but precision in definition is extremely important to me, largely because I work with such abstra...