Thereās a new problem. To track twelve directions, we need to figure out how to time the updated coordinates so it would predict where the trajectory would go.
Think of it like BHās graphing calculator. The game is the graph, and weāre using functions to help us guide the pseudo-projectile.
Remember, rise over run:
For the northeast directions, youād need to track if the function is (Y)2/1(X) or (Y)1/2(X), all positives.
For the southeast directions, youād need to have the Y in the negatives and X in the positives.
For the southwest directions, youād need to have both X and Y in the negatives.
For the northwest directions, youād need to have X in the negatives and Y in the positives.
There are no straight diagonals; there are only split diagonals and straight cardinals.
I need to know when to time it, e.g. 0.3 seconds, by knowing the gadget speed. There will be 3 categories:
Slow (Such as the Quantum Portal)
Average (Such as the P.M.L or something else)
Fast (Such as the Blaster, my beloved)
This needs to be listed for every gadget.
Gosh, after this is finished people will think itās a GitHub plugin, looking at the code.
The Timekeeper speed isnāt listed, so Iām putting it at medium. Iāve got them all!.. but we still need timing for each category.
Zapper: Average
Wooden Wand: Average
Blaster[1]: Fast
Snowball Launcher: Average
P.M.L.: Average
Slingshot: Fast
Evil Eye: Slow
Quantum Portal: Slow
Pixelator: Average
Stoneburster: Average
Twister: Average
Prickler: Average
Fill in the blank:
Slow Timing: 0._ seconds
Average Timing: 0._ seconds
Fast Timing: 0._ seconds
Wel letās seeā¦Iām choosing one from each category and shooting them across 7 blocks of terrain to see their speed
Prickler - 0.97 secs over 7 blocks
Blaster - 0.37 secs over 7 blocks (waow)
Quantum Portal - 1.78 secs over 7 blocks
So given that the speed of a fast gadget is abt 18.198 bps (blocks per sec), average gadgets is abt 7.216 bps and slow ones take like 4 bps, now we just fill in the blanks with a little math:
Actually wait we need to use seconds per block
fast = 0.0528571429 spb
average = 0.138571429 spb
slow = 0.254285714 spb
So, i believe the timing would be the spb of each cat.
However, because i chose a ārepresentativeā for each cat, this means that the above result arenāt thatā¦accurate. If you want total accuracy, then weāre gonna have to test each gadget and average each cat of gadget. My current suggestion however is to just test the numbers we have rn, and worry about the overall later.
It needs to be simpler. To be frank, only one check needs to occur, somewhere in the middle of the whole trajectory. This trades off a bit of accuracy, but it leans more to efficiency than it backs away from accuracy.
What is a ācatā :\
Donāt get arrogant. I know something you donāt, Boss_1-
Get out, ego. Seriously.
I forgor that we need the range of each gadget, so the number of checks vary for each gadget