|
|||
| Views: 693,395 | 06-28-21, 01:22 am | ||
|
|||
| Views: 693,395 | 06-28-21, 01:22 am | ||
code block | Thread review | |
|---|---|
| PillowShout | Yeah that seems to have fixed it. I'll let you know if I find anything else. |
| Kawa |
That thing with the replacement tokens is not the intended behavior, and I'm gonna look at it right now. Edit: //message = message.Replace(replace, with);
var left = message.Substring(0, match.Groups[0].Index); var right = message.Substring(match.Groups[0].Index + match.Groups[0].Length); message = left + with + right; |
| PillowShout |
I noticed a couple of bugs to do with text generation. The first bug is that body parts with the virgin token that don't already have looseness and wetness values aren't returning anything. I'm not sure if this is an oversight where the looseness and wetness values weren't added in the bodyplan when they should have been, or if the parts with the virgin token were intended to autogenerate those values but aren't generating them. Either way this is producing some erronius results when the looseness or wetness values are accessed for these parts. Bug number two may actually not be a bug, in which case I have a question about how to work around it. When the parser replaces tokens in a scene, each token of the same type is replaced with the exact same string, even when they could be replaced differently. For example, if I write "[cockrand] [cockrand] [cockrand]", it comes back with "dick dick dick" or "penis penis penis" instead of what I was expecting which is "cock prick penis". I understand if this is the intended behavior, but in that case how do I work around it? |