MCBICK'S PROFILE

Ok after some testing it only seems to be slightly faster, maybe 2-3 seconds faster. I thought I found the solution to make this event work, but guess not. I think it's because it cycles one part about 48,000 times or more total(Scanning entire screen), just a rough estimate. It's the part in your trigo script where it checks SIGHTEND is less than GUARDX. I created a counter to check how many times it cycles through that and it ranges from 30-350 per tile. It has to execute 10(commands) x 48,000(cycles) which is way more than the 10k limit per frame.

Edit: Do Dyn plugins operate outside of the 2k3 engine? If it does then I can try to use that to eliminate the 10k limit.

Oh so if i just use label loops instead I'll be fine? The event I am talking about checks every tile on the screen and will create a black tile if your character's view is obstructed. To check every tile it takes about 5-10 seconds depending on where the character is located relative to the screen, this can be optimized to reduce the total time to 5-6 seconds. I have to combine 2 pages of coding into one to try it though, as it is now it cycles through 2 pages in the event.

Edit: By my estimate I should save 5.12 seconds since it cycles through 320(Every tile on screen) times which is 320 invisible 0.0 waits.

Edit2: Might save even more time since I only counted one page, but it cycles through 2 pages of an event.

@Kazesui
What hidden 0.0 wait? Also don't loops like this cause lag in 2k3?

How do you decrease it from .1 wait? I tried 0.0 and it doesn't add to the step counter.

I tried wait 0.0 and it doesn't add to the counter most likely because the two sets of variables are always the same.

Edit: I did figure out a way for an exact step counter, but it involves conditions which mess with the HP. The problem with that though is I'll see a red flash every time I walk.