Not A Bug Gump IDs changing post reboot

[amelia ketel]

15/09/2020 gump ids for blacksmith were 0xc69ca0a4 and for tracking were 0xeeca85a8.
16/09/2020 gump ids for blacksmith were 0x1ee79997 and for tracking were 0x71c0ef18.

 

[Dan]

The team will need a lot more context here, please.

 

[amelia ketel]

When running any of my UOSteam macros, they run fine pre-server reboot. Once the server is rebooted, all of the gump IDs need to be updated with new IDs. This is happening to other people who have mentioned this in Discord. Once i change my gump IDs in my scripts, they then work perfectly fine if i restart my client / pc, even if i update my client. Once the shard is rebooted at 11am GMT (for me) those gump IDs no longer work and need to be updated again. I have experienced this elsewhere before, playing on UO Outlands, Luthius their lead developer fixed this, i believe they had this problem when they migrated their code from one server to another. His Discord is Luthius#3011. If further information is required please state what exactly and i can try and obtain you further proof. I hope this helps somewhat more than my original posting.

 

[Dan]

I almost wonder if it's the server being .core vs .framework. We had moved to to core about a week ago and just changed back to framework while we work out some other core bugs.

Let me know after the next 6am daily restart if they are still doing this.

 

[amelia ketel]

No worries will do, it might be that change that is causing this. And if you have flipped back, it explains why its changed again.

 

[amelia ketel]

Woke up this morning and gump id for tracking had changed to 0xb16e7d71. Havent checked blacksmith but assume it has. This is pre normal 11am GMT reboot, but unsure if another reboot happened last night due to the Clients being updated by OSI

 

[amelia ketel]

Interestingly after the usual reboot today, the gumps have not changed. If you have switched back to framework, and this wasnt an issue before then i assume this is working as it was before you switched to core. maybe switching to core is what is causing this. (theory)

 

[Dan]

Yeah, could just be the way .net core cached the info.

 

[amelia ketel]

So i spoke to a friend who helps with dev on CUO, he said to me that he remembers the problem being when they moved over to .net core. Suggested who i should ask about what they did to resolve it. Now im wondering if going over to .net core and, if once they change once will they change every reboot. I cant remember if that was one of the cases where it happened. I will see if the dev who supposedly resolved this has any further information for us.