- Joined
- Jul 14, 2018
- Posts
- 15
Hey all! I came across a peculiar issue today.
I wanted to split the route I was working on, Route 12, into two maps as it was going to be fairly long one. So, I created the two maps in RMXP, both named Route 12, one parented by the other. I added encounter data to both of them, and then C/Ped one of the Route 12's encounters to the other. The encounters.txt file looked like this:
In this case, Map ID 46 was the parent to Map ID 51. In Map ID 46, the encounters worked completely fine. However, in Map ID 51, the encounters levels were in the range of 95-97 (? - I'm not entirely sure the exact range, but definitely not what was explicitly declared in the encounters.txt file). The species that I encountered were correct, but the levels were way off. I assumed Essentials may not like that both maps were named the same, so I changed this map to a different name; "Route 12 2". The issue persisted.
I actually managed to solve this through a tedious workaround - I created a new map named "Route 122" (still unsure if the name was the problem; this could be arbitrary), added the encounter data to the new map, and then I slowly copied the tiles and events from Map ID 51 into the new map (ID 52), one by one, checking after each copy if the level error came back. It never did; it seems to be working with the new map.
So my question is, does anyone know why this actually happened? I'm a little skeptical that it was because I named both maps the same thing before adding encounter data to the .txt file. If anyone knows, that would be helpful in case I or anyone else comes across this in the future. Luckily the map in question was rather small with not many events so it wasn't a big time suck to recreate it. Also, I did surf around a bit and try to see if a thread already exists with this issue but I couldn't find one, so sorry if this has already been documented somewhere.
I wanted to split the route I was working on, Route 12, into two maps as it was going to be fairly long one. So, I created the two maps in RMXP, both named Route 12, one parented by the other. I added encounter data to both of them, and then C/Ped one of the Route 12's encounters to the other. The encounters.txt file looked like this:
Code:
#-------------------------------
046 # Route 12
25,10,10
Land
ZIDNA,22,25
DINGOL,24,25
AMPIARY,20,22
TANBARA,22,25
GRANPEDE,22,25
TAZORCH,22,25
DANDRIFTA,23,25
PUKABARN,23,25
AMPIARY,25
ALLONO,25
ALLONO,25
TANBARA,27
#-------------------------------
051 # Route 12
25,10,10
Land
ZIDNA,22,25
DINGOL,24,25
AMPIARY,20,22
TANBARA,22,25
GRANPEDE,22,25
TAZORCH,22,25
DANDRIFTA,23,25
PUKABARN,23,25
AMPIARY,25
ALLONO,25
ALLONO,25
TANBARA,27
#-------------------------------In this case, Map ID 46 was the parent to Map ID 51. In Map ID 46, the encounters worked completely fine. However, in Map ID 51, the encounters levels were in the range of 95-97 (? - I'm not entirely sure the exact range, but definitely not what was explicitly declared in the encounters.txt file). The species that I encountered were correct, but the levels were way off. I assumed Essentials may not like that both maps were named the same, so I changed this map to a different name; "Route 12 2". The issue persisted.
I actually managed to solve this through a tedious workaround - I created a new map named "Route 122" (still unsure if the name was the problem; this could be arbitrary), added the encounter data to the new map, and then I slowly copied the tiles and events from Map ID 51 into the new map (ID 52), one by one, checking after each copy if the level error came back. It never did; it seems to be working with the new map.
So my question is, does anyone know why this actually happened? I'm a little skeptical that it was because I named both maps the same thing before adding encounter data to the .txt file. If anyone knows, that would be helpful in case I or anyone else comes across this in the future. Luckily the map in question was rather small with not many events so it wasn't a big time suck to recreate it. Also, I did surf around a bit and try to see if a thread already exists with this issue but I couldn't find one, so sorry if this has already been documented somewhere.
