Building the Megaverse takes time and brilliance, it can't be done at once.
Building the Megaverse happened in three steps.
The goal matrix shows that there is symmetry drawn around row and col 13 so there are four petals in four qudrants
So, getting the POLYanets 🪐 in place requires running the same code to planet the POLYanets 🪐 in each qudrant but with a twist of the indices based on which quadrant is targeted using the a transformation built for that.
Inside each quadrant, there is also a pattern that shows it can be done in steps of filling two in a row then two in a column, and then repeat in the opposite order.
Here a mapping table is used extracted from the goals matrix to sprinkle the 🌙SOLoons each in its position, there was no pattern identfied. A check point is to make sure that the sent to index is adjacent to a 🪐POLYanet.
As the guardians of the Megaverse, the same approach of a mapping table is used extracted from the goals matrix to throw the ☄COMETHs and scatter them across the Megaverse.
As expected, building a Megaverse is full of surprises, physics can't yet explain all about it, so glitches were handled by adding a timing and retry interceptor to resend objects into the Megaverse if Law of HTTP produced the 429 constant.
A simple colorful astor-console displays what is happening as objects gets sent into the Megaverse.
$ npm installTo run phase 1 run
$ npm run start:phase1To run phase 2 run
$ npm run start:phase2To wipe a single index and replace it with SPACE run
$ npm run start:wipe -- --action one --index row,colTo wipe entire Megaverse and replace it with all SPACEs
$ npm run start:wipe -- --action allTo extract the indices for 🌙SOLOONs and ☄COMETHs run this command
$ npm run extract- Author - Ahmad Sghaier
- Twitter - @ahmad_sghaier