xmoonproductions.org
https://www.xmoonproductions.org/

Possible bug in the language or compiler.
https://www.xmoonproductions.org/viewtopic.php?f=27&t=3512		 Page 1 of 1
Author:  TheMohawkNinja [ Mon Dec 15, 2014 8:39 pm ]
Post subject:  Possible bug in the language or compiler.
So, I started experimenting with using the talk.s function as a method of debugging mods, but in my experiments, whether or not a talk.s line would be executed seemed to be entirely dependent on whether or not it was after a variable value change, which from my knowledge of coding, shouldn't happen whatsoever.

Specifically, the debugging talk.s line won't output when it is coded like this:
Code:
[state.dyn.me.coll.vag_deep.obj_par>=3]
{
   talk.s="DEBUG: Been penetrated at depth of 3";
   state.dyn.me.state.beenpen=true;
   talk.s="Ouch!";
}


but it will output when it is coded like this:
Code:
[state.dyn.me.coll.vag_deep.obj_par>=3]
{
   state.dyn.me.state.beenpen=true;
   talk.s="Ouch!";
   talk.s="DEBUG: Been penetrated at depth of 3";
}


NOTE: state.dyn.me.state.beenpen is a user-defined global variable.

I can't figure it out, because all the global variable does, is keep track of whether or not you entered the girl's vagina or not.
Author:  xpadmin [ Mon Dec 15, 2014 10:46 pm ]
Post subject:  Re: Possible bug in the language or compiler.
Difficult to say what goes wrong in the code.
Settings the talk.s twice will overwrite previous value.

For tracing best is to use Trace("Debug: text");
Page 1 of 1 All times are UTC
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/