ExpertLotto.com

It rejects all the draws on the backtest no matter the settings you make as input.
Could you explain to me, please, (like for a 2 yo kid) what exactly it does with more draw examples?
Thank you so much in advance!

This plugin filters for two groups of right-most digits(or last digits) that follow one another. The digits groups are 1,2,3(Core) and 4,5,6,7,8,9,0(Non-Core). Example of 'right-most' digits in a ticket in red here-> 07,21,26,27,33,48. Then select an option for a Min/Max of digits from four setup orders.

The digit setup orders are;
Core to Core: = 1,2,3 followed by 1,2,3.
Core to Non-Core: = 1,2,3 followed by 4,5,6,7,8,9,0.
Non-Core to Non-Core: = 4,5,6,7,8,9,0 followed by 4,5,6,7,8,9,0.
Non-Core to Core: = 4,5,6,7,8,9,0 followed by 1,2,3.

Examples;
Core to Core: Min [1] Max [1] : Accept
- Ticket 03,23,24,34,45,48 is accepted because [1] Core digit is followed by another Core digit.
Core to Core: Min [2] Max [2] : Accept
- Ticket 02,12,23,35,36,49 is accepted because [2] Core digits are followed by other Core digits.
- Ticket 21,22,28,32,41,45 is accepted because [2] Core digits are followed by other Core digits.
Core to Core: Min [2] Max [4] : Accept
- Ticket 04,25,31,32,41,43 is accepted because [3] Core digits are followed by other Core digits.
- Ticket 11,12,21,23,33,41 is rejected because [5] Core digits are followed by other Core digits, and the condition allows for only Max [4].

The documentation listed in the filter and 'Help' for this plugin seems to be missing some key information/terminology. However, I back-tested the plugin on my system and it filters correctly. Any questions, or I missed something, let me know.

tdnl46w wrote:This plugin filters for two groups of right-most digits(or last digits) that follow one another. The digits groups are 1,2,3(Core) and 4,5,6,7,8,9,0(Non-Core). Example of 'right-most' digits in a ticket in red here-> 07,21,26,27,33,48. Then select an option for a Min/Max of digits from four setup orders.

The digit setup orders are;
Core to Core: = 1,2,3 followed by 1,2,3.
Core to Non-Core: = 1,2,3 followed by 4,5,6,7,8,9,0.
Non-Core to Non-Core: = 4,5,6,7,8,9,0 followed by 4,5,6,7,8,9,0.
Non-Core to Core: = 4,5,6,7,8,9,0 followed by 1,2,3.

Examples;
Core to Core: Min [1] Max [1] : Accept
- Ticket 03,23,24,34,45,48 is accepted because [1] Core digit is followed by another Core digit.
Core to Core: Min [2] Max [2] : Accept
- Ticket 02,12,23,35,36,49 is accepted because [2] Core digits are followed by other Core digits.
- Ticket 21,22,28,32,41,45 is accepted because [2] Core digits are followed by other Core digits.
Core to Core: Min [2] Max [4] : Accept
- Ticket 04,25,31,32,41,43 is accepted because [3] Core digits are followed by other Core digits.
- Ticket 11,12,21,23,33,41 is rejected because [5] Core digits are followed by other Core digits, and the condition allows for only Max [4].

The documentation listed in the filter and 'Help' for this plugin seems to be missing some key information/terminology. However, I back-tested the plugin on my system and it filters correctly. Any questions, or I missed something, let me know.

Core to Core: Min [1] Max [1] : Accept
- Ticket 03,23,24,34,45,48 is accepted because [1] Core digit is followed by another Core digit.

So, there are totally 2 digits and not a single one. Then, Min[1] and Max[1] whare are referring to? What they mean? What they represent?

Could you give a rejection example too for this situation, please?

Core to Core: Min [2] Max [2] : Accept
- Ticket 02,12,23,35,36,49 is accepted because [2] Core digits are followed by other Core digits.

But they are 3 digits in total it shouldn't be 4 if following the rules?

Core to Core: Min [2] Max [2] : Accept
- Ticket 21,22,28,32,41,45 is accepted because [2] Core digits are followed by other Core digits.

Also, there are 4 digits but they are separated by a noncore digit 8. Is this an accepted situation since they are separated by a noncore digit 8 and this means they do not follow exactly by other 2?

Could you give a rejection example for each of these situations, please?

The digit setup orders are;
Core to Core: = 1,2,3 followed by 1,2,3.
Core to Non-Core: = 1,2,3 followed by 4,5,6,7,8,9,0.
Non-Core to Non-Core: = 4,5,6,7,8,9,0 followed by 4,5,6,7,8,9,0.
Non-Core to Core: = 4,5,6,7,8,9,0 followed by 1,2,3.

Also, could you give an example about all these situations above?

Non-Core to Non-Core: = 4,5,6,7,8,9,0 followed by 4,5,6,7,8,9,0.

How is that? It is not the same? Could you give to me, please, some accepted and rejection situations, please?

Thank you so much in advance!

Core to Core, Non-Core to Core(etc.), are referring to instances of adjacent digits in a ticket. The Min/Max are the counts of these instances. This plugin is simply splitting two groups of last digits into four group to group setups.

So in the filter example;
Core to Core: Min [2] Max [2] : Accept <---this means it will filter and accept exactly two Core to Core instances in a ticket.
-Ticket 02,12,23,35,36,49 is accepted because [2] Core digits are followed by other Core digits. <---this ticket has exactly two instances of adjacent Core digits. Instance one, Core digit 2 in ticket number 02 is adjacent to Core digit 2 in ticket number 12, and instance two, Core digit 2 in ticket number 12 is adjacent to Core digit 3 in ticket number 23.