Help with Script

[sincla]

Do I need to buy the license for d20 to get the pkg files? I mean, what do I have to do to see the source code in .pkg files.

[AndrewD2]

pkg files are like a zip file, you can't access the stuff in them (and they can't be unzipped) I don't believe you can get access to that stuff from the D20 system

[sincla]

Damn, it would have been really helpful to me to see how they are structured. But I guess I understand it it's proprietary stuff. But one wonders then how the community creates open source material for d20 if they don't know how the basic files are structured and specified.

[AndrewD2]

You can do a lot with the editor already, you don't need to authoring kit for doing that stuff.

[sincla]

The wiki says that the intersect reference is the following format:

intersect[init,curr]

where in a validate script the tags in the group init belong to the initial context, that is the prospective container for a thing, and the curr gives you the tags in the alternate context which is the thing that might be added (as a pick).

But, it seems that this is exactly backwards in many instances in actual code I've seen. For example:

altthing.intersect[ReqClass,Class]

where the script is comparing the required class to wield the thing to be added (ReqClass) which resides on the altthing, and seeing if that intersects with a Class tag on the hero.

Which is the correct syntax?

[sincla]

Still could use an answer on this...anyone know if the wiki has the context parameters in the square brackets exactly backwards?

[Colen]

After looking at the code, it looks like you're right - the first parameter is the tag group to look at in the context you've just transitioned to, while the second parameter is the tag group to look at in the overall context for the script.

Thanks for flagging this! I'll update the documentation appropriately.

[sincla]

Please do a quick double check of my source. I got the above code snippet from the 4e data files, components.core, the Requires component, which is full of validate scripts like these.

[sincla]

Hi Colen,

I'm now getting an incomprehensible "Portal 'level" - Reference to incompatible field type/style/behavior based on portal type" for the following portal element:

	<portal
      id="level"
      style="lblNormal"
      showinvalid="yes">
      <label>
		  <labeltext><![CDATA[
		    @text = "hello world"
		    ]]></labeltext>
		</label>
	</portal>

Thing is I didn't change anything at all about it to cause the error. The only thing I tried was to change the text output to a simple string to see if even that would work, and it doesn't.

[Mathias]

What's the code you changed it to?