Hi all,
I opened a new thread since I've found a weird behavior in the
preview scene I posted inside the “RBD impact data” threat related
to the “stamp” function.

Now, if you download the scene, you will see I'm trying to emit particles
at impact position, and I'm using “stamp” to pass the correct number
of group I'm using inside the DOPnet.

If you go inside the “forEach” node and look inside the “point”node (for example), inside position I'm fetching the "position“ data from the Impacts data and I'm using ”stamp" to correctly stamp the group number.

My expression is:

dopfield(“/obj/dopnet”, “shatter_” + padzero(2, stamp(“..”, “FORVALUE”, 0)), “Impacts”, “Impacts”, $PT, “positionx”)

Now, “stamp” should use “0” as <default> value if thvalue to use ise <token> does not existent.

During my test I noticed that there was something wrong in the result I was getting and seemed to me that something was not
taking into account, so, just for curiosity I changed the <default> value from “0” to “2”, and I start to get some different result, you can see this inside the field that get update every frames..

For example, if you go to frame 16, and you change from “0” to “2” you will se that
you get some value instead of ZERO….

Am I missing something?
Should be the <default> value used only if the <token> does not exist, so
no matter what the <default> value is as soon the <token> exist??

Many thank you,

AlexNardini