I have a going theory that the “new URL bug” is partially caused by the 31-bit Steam ID rollover (maps with IDs greater than 2147483647).
Here is Geneosis’s method for using Cheat Engine to update maps.
The first publish sets the “current item ID” variable to a known value, you use Cheat Engine to find this value and replace it with the correct one, and then publishing uses the correct value.
.p2c
for the map you want to publish. Convert
the FileID
to a signed 32-bit integer which I will
call the “truncated ID”.Of course this will not work for all republishing situations - Geneosis’s guide is from 2013, so apparently the new-URL bug predates the item ID rollover.
My theory is that these days, you can’t fix URL bugs by modifying the p2c (Bisqwit’s method) because the game always truncates the file ID to 32 bits while loading the file. But the variable used to hold the item ID is ultimately 64 bits which is why replacing it using Cheat Engine works.
I will republish “Destack”: https://steamcommunity.com/sharedfiles/filedetails/?id=3425844055
This item has ID 3425844055
in base 10.
0x00000000CC323B57
.QWORD
, DWORD
, WORD
, or
BYTE
; cycle it to QWORD
(64-bits).HEX
and paste in the hex file ID. In my case,
I paste in 0x00000000CC323B57
.DEC
, verify that this matches the item ID of
the published map. I can see the number 3,425,844,055
which
does indeed match.QWORD
label one time, cycling to
DWORD
mode (32 bits). The decimal readout now says
-869,123,241
for me.
Testing workarounds for the URL bug is a hell of a time to not get the URL bug