05-26-2024, 04:09 AM
(This post was last modified: 05-26-2024, 04:09 AM by DerVVulfman.)
BUMP
to version 1.4
Okay...
Well, I looked into it further. The command_end method in the Interpreter class contains the 'unlock' parameter, but more was that kyonides made mention of an internal variable. A clue? Indeed.
The events that were copied were very much exact copies of the original event. Unfortunately, that was the problem. The copies were TOO exact. The duplicates themselves contained data claiming to reside at the x/y coordinates of the original event. But moreso, they still retained within them the original ID. If there were fifteen events on the current map, and you created a duplicate, this 16th event should have an ID of 16 within.
This was sadly not the case... at that time. Events need that internal ID value to function. While messages worked, event erasure, custom graphic changes for a specific 'copy' event would not take place, or anything specific to the event as an individual was non-functional
But now, the new code re-defines the ID of the event as well as its x/y coordinates within its structure before it is actively created and placed upon the map.