BIG MAPS

[DerVVulfman]

Placement is key. Within the KNOWN / TESTED WITH THE FOLLOWING section, I note that it works with Zeriab's Anti-Lag. But that Zeriab's Anti-Lag needs to be above BigMaps.

You see, BigMaps actively changes one of Zeriab's functions, the check_events method you are having issues. It was necessary to pass into it whether the check_events system was going to acquire normal map/event_id combinations for the SPECIAL_UPDATE_IDS test, or whether it needed to find the original map/event_id from a newly created BigMap event.

So BigMaps needs to be below Zeriab's system.

OR you can rip the code from Big Maps and paste my edited rendition of check_events into Zeriab's code (not recommended).