[ACE] Event Offset Repositioning is Visible!

[FeaR616]

hello again fellow, sorry to bother you so much...

I use this Event Fine Tuning Script to ... well.. tune some events, like set an offset for a large gate to put it in the middle.

and here is the problem with this offset: if you teleport from another map to one with events that have offsets, the repositioning of that event is visible... which should not be because it looks weird while gaming.

I made a gif to see exactly what I mean: GIF here!

I tried a workaround with a wait command after the teleports post_transfer method...

I tried, somehow no wait command works...

Spoiler

these wait commands...

Wait(n)# From a move route or something like that, you'd need the following:SceneManager.scene.wait(x)#The following should work as well from anywhere.x.times { Fiber.yield }

what should I do to solve the problem so the repositioning isn't visible for the player??

 

[Nicke]

Create a new event that setup the fine tuning stuff and put that as a parallel process. Change the event speed to 6 (faster) and the freq to 5 (highest).

 

[cabfe]

Just set the frequency of the Event to highest (5) and it should work.

 

[FeaR616]

okay... both fix it. but... why?

I don't understand it ...

 

[cabfe]

Having a high frequency makes the event's command start sooner, even before the map is drawn when set to 5.

No need for a parallel setting actually.

 

[FeaR616]

ooh, that is good to know. thank you very much! =)

 

[seita]

Actually parallel process is important. If you were to do it during an autorun, the autorun waits for the rest of the map setup processes to finish, including the fade-in effect most people use. Parallel process starts immediately and ignores the rest of the map setup processes, so it'll do the fine tuning immediately during the fade-in.

 

[FeaR616]

as the offset for the events works properly when frequency is set to 5, there is no need for THAT point to be parallel or autorun.

but good information about general parallel processes and autorun events. =)

 

[cabfe]

Actually parallel process is important. If you were to do it during an autorun, the autorun waits for the rest of the map setup processes to finish, including the fade-in effect most people use. Parallel process starts immediately and ignores the rest of the map setup processes, so it'll do the fine tuning immediately during the fade-in.

I know and agree about the parallel process starting before the autorun, but since this command is put inside an event, setting its frequency to 5 always works, even if called within a move route inside an autorun to be displayed after the drawing of the map.