Lol thanks! I managed to create most of those over the weekend. May seem quick, but like I mentioned before I had created "half functional" versions of those addons on Ace, so I mainly took 1 day to rewrite in JS then like another day to rewrite it, but better and hopefully more optimized, spent a few days adding the missing features + testing. So next massive updates might not be for awhile since I have nothing else planned for now ( actually that's a lie, I have a secret "awesome?" addon idea that I'll attempt on the weekend. )
As for that zoom depths, I would recommend looking at the
.onDepthChange() and
.depth() functions so you can get an idea on how I was remembering previous depths ( used for bridges ) But for you case kind of sounds like you don't want to just keep the previous one, but all previous ones, so you'll probably use an array and push previous depths inside of it, and in the
.onZoomDepthChange() check if the new zoom depth is in that array if it is, do nothing. You should probably also store just the color instead of the zoom value in case you want different colors with same zoom values if you want to go back to a zoom.
If you want more of my thoughts on this, feel free to pm me.
** I also forgot to mention that my Sight script will ignore Collision Maps. You can try turning on "Convert Collision Map" option in Movement script, but depending on you collision map, that might cause serious performance issues. When I attempted it with my Q collision map, I couldn't even move once I got in range lol, this is because it created like 300+ boxes, so the script is making a shadow for 300+ boxes and checking if you're inside any of those 300+ boxes shadow. I already have a few ideas on how to fix it but I have Zero clue on how to implement a user friendly fix right now.
In case anyones willing to share ideas, here are my thoughts:
Spoiler
Fix 1. Rewrite my convert collision map function, to create a polygon instead. ( Have 0 clue on how to do this right now )
Fix 2. Make another JSON file and have you manually create the polygons, which would be an array with pixel coordinates.
For creating the polygon you don't have to go selecting every pixel surrounding the collision, you can do something as basic as:
* Blue dots being points I would pick.
You might notice there's hardly any points. Will this even work? In my head I see it working perfectly, but I wouldn't know for sure until I test it.
And also, how do you guys feel about JSON files? Should I keep using them or should I have you make them inside the js file instead? I'm planning on making another addon that can load / edit JSON files related to only my Scripts.
Example of editing the RegionBoxes.json:
It'll load all the current Regions into a menu as a list with "Add new Region" on bottom of list, and have a button that can delete the selected region.
When you click on a Region you will see a list of all current boxes and a "Add new box" on bottom of the list, plus the a button to delete the selected box.
When you click on the Box you will see all the possible options for it; width, height, ox, oy, and tag
And that's it, simple as that.
But I just want to know how you guys feel about them first. Maybe that addon will change your mind on them?
