Solved Adding additional world to Colosseum

[Kyraie]

Hey guys!
I was hoping to get a bit brighter and educated on what I'm doing wrong when trying to add another world into Colosseum. So I'm trying to add different worlds depending on different modes for Colosseum, I've taken the original Colosseum map and re-textured it, added it to Coreserver.ini and added it to the corresponding resource files.

However when loading the map in Colosseum.cpp as another map depending on what mode you are in i get the error.

Layer not found

No more details on the error, I tried to look up where the error is generated and following the callstack with breakpoints but nothing works for me, I tried to look if the core server or the world server initiates linkmap for colosseum on startup but nothing is helping me.

Would love to get some help with this.

 

[Fliperworld]

From what I understand, you're attempting to achieve two different tasks:
1-Adding a new map, even if it's identical to another one but with different textures.
2-Modifying the Colosseum system to utilize two different maps.

We can't pinpoint the exact issue without more information. It's possible the new map isn't loading at all, or the Colosseum system hasn't been fully adjusted to handle two maps. Since you're debugging the code where the error occurs, only you can determine if the problem lies in pTargetWorld not existing or nLayer missing in the link map.

Please provide details of all the changes you've made (World.inc, defineWorld.h, world.txt.txt, Colosseum.cpp/h), so we can assist in identifying the error.

Additionally, let us know the version of the server files being used. There could be significant differences between versions, such as retail 21.2 which not even uses Colosseum.cpp/h.

To diagnose the issue, here are the steps I would suggest:
A)-Confirm if the new map has loaded by testing teleportation to it.
B)-Make a simple adjustment in Colosseum.cpp to always use the new map instead of WI_WORLD_COLOSSEUM.
These tests focus specifically on adding a new map. If everything works as expected, the issue likely lies in the implementation of the system for using different maps in Colosseum.cpp.

 

[Kyraie]

From what I understand, you're attempting to achieve two different tasks:
1-Adding a new map, even if it's identical to another one but with different textures.
2-Modifying the Colosseum system to utilize two different maps.

We can't pinpoint the exact issue without more information. It's possible the new map isn't loading at all, or the Colosseum system hasn't been fully adjusted to handle two maps. Since you're debugging the code where the error occurs, only you can determine if the problem lies in pTargetWorld not existing or nLayer missing in the link map.

Please provide details of all the changes you've made (World.inc, defineWorld.h, world.txt.txt, Colosseum.cpp/h), so we can assist in identifying the error.

Additionally, let us know the version of the server files being used. There could be significant differences between versions, such as retail 21.2 which not even uses Colosseum.cpp/h.

To diagnose the issue, here are the steps I would suggest:
A)-Confirm if the new map has loaded by testing teleportation to it.
B)-Make a simple adjustment in Colosseum.cpp to always use the new map instead of WI_WORLD_COLOSSEUM.
These tests focus specifically on adding a new map. If everything works as expected, the issue likely lies in the implementation of the system for using different maps in Colosseum.cpp.

So obviously I forgot to mention what files I’m using, I’m using the L19.4 files.
As for the rest, the World.inc, defineWorld.h, world.txt.txt looks exactly like how basic implementation of a map would look like, but I'll add the added lines.

World.inc

Please login and(or) register to see this awesome content today.

defineWorld.h (Note that I've changed WI_WORLD_ARENA_1 to increment by +1 and the following worlds)

Please login and(or) register to see this awesome content today.

As for Colosseum.cpp I've made checks on what mode you've entered on. Examples lines

Please login and(or) register to see this awesome content today.

While making this reply

I had to test your suggestions and further inspecting the breakpoints I noticed a call from CColosseumMng: Process(), so I followed each step and got to my check i added when i re-did colosseum (I removed the Colosseum.lua and added my own spawn list per mode, I noticed that the Fire mode was missing in that, I was pretty sure I added it when I made the file however checking github pushes I clearly removed it when testing other stuff)

Please login and(or) register to see this awesome content today.

Conclusion, I fucked up and forgot to add the spawn list for fire mode hence why the mode was always failing and resulting in no layer found.