easter egg in the thumbnail :) -- {THIS SPRITE DOES NOT AUTOMATICALLY FIX YOUR PROJECT, IT HELPS YOU.} -- Introducing the engine, Sprite.Debugger! It helps you debug sprites! (duh) Ok, so I may have gotten inspired by RStudio to make this project, so, here it is! This was made in 3 hrs despite having such a simple concept and yet has 1304 blocks alone to itself. (1305 if the define block counts.) No one is going to see this project, and that's okay. At this point im talking to a brick wall :D This fancy new (and LARGE) code has many features, so heres all of them with parentheses to explain it. - Print / Warn (By Print / Warn, I mean, add things to the list I provided in this project. Print just adds the info you send below, warn sends things to the top, making them have more priority. - Send Info (Basically like Print / Warn. You get to send any silly little message to the console for debug purposes. - Costume Name (reply with true/false) (When using this, the message that has this enabled will show what costume sent this debug message. Unfortunately, Scratch can't show what Sprite sent the debug message.) - Costume Number (reply with true/false) (Same as Costume Name except it shows what costume # sent the debug message instead of the costume name.) - Time (reply with true/false) (Shows you the exact hour, minute, and second the debug message was sent.) - Prints/Warns (reply with true/false) (Don't get this mistaken with the "Print / Warn" feature. This one lets you know if the debug message had a Printed or Warned property, making it organized for you.) - Notifs (reply with true/false) (Basically this tells you what other properties are enabled.) And that's all! You might be asking yourself, how is this useful? And, I thought that too. But, if your code isn't working and you would like to find out, just place this big titan in your project, put some debug blocks and enable some properties to your liking, then, you will have a better chance finding out what part of your code is flawed. Popular uses: - Showing what values variables had at the time - Updating whatever action was done - Provide insights on a piece of code - Printing specific values of something (booleans, operators, statements, etc) - Acting like you know what your doing Thank you for reading my yap session (if you did)
