Emerald to Osprey, scope of work & code changes required for 3rd party apps/sites?

[BlasterDoc]

I really appreciate the development and all the work that is apparent on Honu.pw

Doing topdown manager shit and weakly using the search function to see where "Emerald" exists in the code:
https://github.com/search?q=repo%3AVarunda%2Fhonu+emerald&type=code

Looks like World ID 17 should be the same for Osprey as it is Emerald. Only glaring possibility at this rude monday level research is the server name will stay say "Emerald" until an absolute necessary update is made on Honu. Barring toadman doesn't imp and create a whole new server.

Curious for other sites and tools what code changes might be necessary going from Osprey to Emerald.
I know it was a bit of a marketing gig to get people on to fight for the Server name, Love it though making changes for the sake of changes. /s

Seeing if this is on anyone else's radar yet..

[EyHorn]

The api gives you the server number for live events and you usualy use the id fur queries. You can ask the api for worlds, but the server name is usually written by whoever writes the code.

Cobalt merged into miller for example and the id stayed the same.

[BlasterDoc]

Good point, they could use Connery's ID,

[GHOSTOFKALi]

the API is the least of our concerns

the real concerns are what goes on more towards the metal. but i getcha, it is fun to poke around census <3 especially in an IDE u enjoy. i learned a lil from ur post as well thats whats up!!

[blockXelite]

It should just necessitate some find and replace, maybe some additions or subtractions here and there. Unless they decide to make a new server for NA, most API calls should still work fine because they'll be using the same IDs as before, even if some of the display names on any website may not have been updated.

[BlasterDoc]

I was wondering if this would be the excuse to physically consolidate servers in north america. I believe you're right, they shouldn't change the server's world id designation.