View unanswered posts | View active topics It is currently Fri Mar 29, 2024 3:39 pm



Reply to topic  [ 2 posts ] 
 Possible bug in the language or compiler. 
Author Message
Rank 16
Rank 16

Joined: Thu Feb 13, 2014 3:54 pm
Posts: 379
Location: United States
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.


Mon Dec 15, 2014 8:39 pm
Profile
Site Admin
Site Admin

Joined: Thu Feb 07, 2013 11:16 am
Posts: 1865
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");


Mon Dec 15, 2014 10:46 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 2 posts ] 

Who is online

Users browsing this forum: No registered users and 37 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group.
Designed by X-Moon Productions.