a tower defence thingy. press s to spawn a saw, then click to place it down. go to the shop below (down arrow) to buy perilous logs (click on em or press l (i should make you able to buy logs anyway when pressing l, but i havent yet, so you still have to go to the shop.)), which'd be the basic shooty tower if they aimed. as seen on the BIG BIT OF TEXT I SHOULD CODE TO ONLY APPEAR WHEN BUYING LOGS, when buying directional stuff, it's the first click for position, second for direction.
day ?, day 1 of sharing: 1/30/23 path, house, and mailman made yesterday pathing code finished today, and spawning code. update 2 (i ain't gonna act like the schedule is consistent anymore, it's APRIL.): consolidated boom script changed spike to saw because yes update 3: you might notice the game looks a little more broken. this is because i'm trying to implement an actual shop rather than "press s and a saw appears because hehehehehe" i have now just realized that gluing a saw to the mouse cursor is not a good idea when the mailmen only check for if they touch a saw (or a good idea to the player for about 5 seconds (spectacle)) update 4: the log tower is here! so is the shop for it! i haven't fixed the game from looking broken, but it's playable now! update 5: i broke the game further and i love it. you may notice that if a log hits a saw, something special happens. (this is purposely broken at the moment, i could fix it but noooooo i want to do the infinilogs. at least for now.) update 6: technical stuff! the path now loads from a list of paths, said paths being lists too, which is really complicated given scratch turns lists onto text, which means you've gotta turn it back into a list, if devs added a way to interface with dropdowns better, this pain wouldn't have to happen. if there was an easy way to delete a part from a string, this pain would be partly mitigated. i've made a block that deletes the last of a string though, so you can toss it in your backpack if ya want. update 7: got that pathing bug fixed explanation: the condition for whether the instruction was a goto or a change to (i don't want to do pythagoras when it aint needed) was whether the last character was not x or not y, and it saw an x, went "that's not a y!", and did a goto when it was supposed to be a change to. also, i've got a semi-level select screen going and a second level in the works! which is odd because i havent even revamped the waves for the first level.
