05-29-2022, 05:54 AM
(This post was last modified: 05-29-2022, 05:59 AM by dale walton.)
Michael, I found a way to do the bug identity check - would you like to collaborate?
I am currently stuck on interpreting the eating rules, because Nick allows a choice of which bug eats which bug.
There are only rare instances where more than one bug could eat, much less where a choice between which eats what would occur, or in which sequence and how that interacts with the don't eat if you can't grow rule. but they affect the structure of the scripting a lot, so I need clarity.
The most true to Nick's purpose, while not requiring lots of exception rules and extra decisions is:
1. Grow or add a bug without merging bugs or exceeding the current size limit
2. Repeat the following steps until it is no longer possible:
A. Choose which bug is hungry and can grow after eating
B. Feed it all the bugs around it that it can eat.
C. Grow this bug.
The resolves questions like, if one bugs can eat both of two bugs, and another bug can eat one of them, but only one can eat (or one can grow in a way that blocks the other from eating, is it required for both prey bugs to get eaten? --- and how to input the decisions required...
Is this how Bug is implemented elsewhere?
It also resolves tree sequence which Nick implies is horizontal, but true horizontal requires capturing the horizontal sequence, or otherwise restricting it.
As mentioned these cases seem rare, -- but when they occur, they could be very important.
BTW, are you working on this for Nick, or is this a private initiative? - I would think Nick might be particular about how the script looks and functions, and thus need to endorse the work.
I am currently stuck on interpreting the eating rules, because Nick allows a choice of which bug eats which bug.
There are only rare instances where more than one bug could eat, much less where a choice between which eats what would occur, or in which sequence and how that interacts with the don't eat if you can't grow rule. but they affect the structure of the scripting a lot, so I need clarity.
The most true to Nick's purpose, while not requiring lots of exception rules and extra decisions is:
1. Grow or add a bug without merging bugs or exceeding the current size limit
2. Repeat the following steps until it is no longer possible:
A. Choose which bug is hungry and can grow after eating
B. Feed it all the bugs around it that it can eat.
C. Grow this bug.
The resolves questions like, if one bugs can eat both of two bugs, and another bug can eat one of them, but only one can eat (or one can grow in a way that blocks the other from eating, is it required for both prey bugs to get eaten? --- and how to input the decisions required...
Is this how Bug is implemented elsewhere?
It also resolves tree sequence which Nick implies is horizontal, but true horizontal requires capturing the horizontal sequence, or otherwise restricting it.
As mentioned these cases seem rare, -- but when they occur, they could be very important.
BTW, are you working on this for Nick, or is this a private initiative? - I would think Nick might be particular about how the script looks and functions, and thus need to endorse the work.