Reply to thread

Message

<blockquote data-quote="Maraxle" data-source="post: 369873" data-attributes="member: 5538">Lots of great questions!&nbsp; I'll try to answer them.The numbers in parentheses do increase the odds of being selected.&nbsp; It works as a percentage, unless the numbers add up to over 100, at which time the program fudges the numbers and takes it out of whatever the total is.&nbsp; I think this is best explained with some examples.Example:#define myexamplefirst (50)second (20)thirdIn this example, first would be chosen 50% of the time, second 20%, and third, the remaining portion (30%).Example2:#define mysecondexampleabc (50)def (50)ghi (50)In this example, since I went over 100% total, the program assumes that I meant to do that.&nbsp; It takes the total out of 150, so abc, def, and ghi each get picked 1/3 (33.3%) of the time.Example3:#define mythirdexamplejklmno (50)pqrIn this final example, mno would be chosen 50% of the time.&nbsp; jkl and pqr would be 25% each.Honestly, I have never tried to see how far it would go.&nbsp; I set no internal limit, so it would vary according to system resources.&nbsp; I generally don't go above 3 or 4, not because of resource issues, but because I haven't written a rule that requires it yet.&nbsp; I may impose an artificial limit in a future revision, simply to avoid throwing the program into a loop.Yes, 50% of the time.&nbsp; Also, you can nest square-brackets.&nbsp; So you can say &quot;[test [test2] ]test3&quot;.&nbsp; 50% of the time it will answer &quot;test3&quot;.&nbsp; 25% of the time it will say &quot;test&nbsp; test3&quot;.&nbsp; The other 25% it will say &quot;test test2 test3&quot;.The technical limit would be ~64,000 bytes long, which would be a lot of parameters.&nbsp; However, like the question about nesting, system resources are the limiting factor.No, thank you.&nbsp; And if you come up with any rules that you would like to share, let me know.&nbsp; Maybe I can include them in a future rule pack.&nbsp; <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" /></blockquote>

[QUOTE="Maraxle, post: 369873, member: 5538"] Lots of great questions! I'll try to answer them. The numbers in parentheses do increase the odds of being selected. It works as a percentage, unless the numbers add up to over 100, at which time the program fudges the numbers and takes it out of whatever the total is. I think this is best explained with some examples. Example: #define myexample first (50) second (20) third In this example, first would be chosen 50% of the time, second 20%, and third, the remaining portion (30%). Example2: #define mysecondexample abc (50) def (50) ghi (50) In this example, since I went over 100% total, the program assumes that I meant to do that. It takes the total out of 150, so abc, def, and ghi each get picked 1/3 (33.3%) of the time. Example3: #define mythirdexample jkl mno (50) pqr In this final example, mno would be chosen 50% of the time. jkl and pqr would be 25% each. Honestly, I have never tried to see how far it would go. I set no internal limit, so it would vary according to system resources. I generally don't go above 3 or 4, not because of resource issues, but because I haven't written a rule that requires it yet. I may impose an artificial limit in a future revision, simply to avoid throwing the program into a loop. Yes, 50% of the time. Also, you can nest square-brackets. So you can say "[test [test2] ]test3". 50% of the time it will answer "test3". 25% of the time it will say "test test3". The other 25% it will say "test test2 test3". The technical limit would be ~64,000 bytes long, which would be a lot of parameters. However, like the question about nesting, system resources are the limiting factor. No, thank you. And if you come up with any rules that you would like to share, let me know. Maybe I can include them in a future rule pack. :) [/QUOTE]

Verification