I also remember this happening right after the Scout update. Don't remember what fixed it - if anything.
On Wed, Mar 18, 2009 at 2:06 PM, Aj Collins <gamerzwo...@gmail.com> wrote: > It was like this for me when the Scout update was released. For the first > few days I could only get like one of the three unlocks to actually be in > my > weapons in one server. Going to a different server seemed to allow for all > the other weapons but the one I could use in the previous server. The bug > went away about a week after the update and haven't had it happen since. > > On Wed, Mar 18, 2009 at 4:56 PM, Emil Larsson <ail...@gmail.com> wrote: > > > Lately I had problems with people not being able to use unlockables on > the > > servers I control. VAC works fine, and TF2 strangely doesn't tell the > > player > > about the server not being connected to Steam (like what usually happens > > during Steam downtimes) in the unlockables screen, so it looks like it's > > working for players in the loadout screen... until they actually try to > > switch to their unlockables. > > > > There's no "steam ticket" problems which usually otherwise happens when > the > > servers are unable to talk with Steam. Restarting fixes the problem > > temporarily, but it crops up 12-24 hours later again. Any ideas? > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlds > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
