Ok, every month we have a new prop of the AC client and every
month we get a rash of people who are unfamiliar with the fact that
the Decal team needs to update the configuration file. However
Decal itself feeds into this rash of incorrect reports of Decal
problems.
What happens at the beginning of the month?
The new prop comes out, player gets the new client and starts
Decal. Decal detects the client version is higher than the
configuration version and asks the user if he wants to update. An
update is performed, Decal continues on. Problem is the
configuration files haven't been updated.
Solution: Add a
check into the update (AutoUpdate.cpp?) which checks the
remote version at some point to see if it actually matches the client
version. If not, inform the user that the Decal configuration files have
not been updated yet, to wait a few hours and try again later. Exit
upon a click of the OK button since it is clear that Decal is in an
unworkable state.
Logged In: YES
user_id=206919
Sounds like a sensible course of action. Of course, finding
someone to actually implement it is another matter :)