Having specific medal datums (or possibly just a proc to do this ourselves) that have all of the possible variable settings for medals. When the server comes online, it will be checked against the current medals on the hub. Any with incorrect info (like modified descriptions) will be automatically updated. Any that don't already exist will be automatically added. They could also automatically be sorted to match the layout in the code. Any that don't exist in the code could be automatically deleted, but that could lead to accidents, better if there was some variable you'd have to set to delete a medal.
As it is now (at least for me) large majority of medal management still goes on inside the game itself. All the hub provides is actual display of them on the website. Which if anything, is just an extra (somewhat tedious) step I have to take.
ID:132898
 Aug 13 2009, 9:16 am
|
|
|
Aug 13 2009, 10:38 am
|
|
Fugsnarf
 |
I'm in favor of this. I think it's a good idea.
|
I see a little problem there when someone is hosting an older version of your game.
| |
Schnitzelnagler wrote:
I see a little problem there when someone is hosting an older version of your game. It could lead to swapping descriptions and such. That's also one of the reasons I suggested having a specific variable available for deletion. If this was made as a proc, or even just a proc in combination with these datums, then developers could easily prevent older versions from updating medal info. Using it as a proc could also allow for in-game medal management. | |
Ruben7 wrote:
Or make a new built in var/hub_version and it syncs with the hub on start up. Isn't that already what world.version is? | |