ram
It's a easy thing to add but at the same time it might affect or influence your stack selection
in a negative way. If you were looking at the number set and had a existing bias for one
digit over another then it could lead you to lean toward your preconceived biased notion for
that value. The idea is to work out the stack value using only the stack data.
This is just my observation but consider this. I have seen many times where users were doing
well in their play only to go the other way when something else was added. Many times we
start our analysis already biased in some way. What we then do is analyze the data looking
for something that confirms a value rather taking what the data says. All you need to do is ask
your self "WHY?" do I need to see the additional information.
When we do stuff like this it often redirects our train of thought in ways that do not help. When
we start adding things it always leads to adding something else and so on. Too much information
is worse than no information at all.
Take the Flip tool for instance, several people are still using it and it has no analysis yet it produces
a lot of box hits.
I then built Flip-II, added a bunch of requested options and it never took off and people went back
to Flip-1. The more stuff I added the more people used it in a way it was not meant to be used.
Not knocking anyone as it's the natural thing to do but winning the lottery is not natural, loosing is.
The Ultra-34 program suffers from too many options which prevents the average user from mastering
any one option. I try to limit my setup to just using rogue and if I can't reach my play budget then
I may not play at all, even on paper. If my rogue setup produces too many lines I will most likely
go back and remove a digit from cells where I had more than one value. I am always working on
new tools but when I play I go rogue.
RL