How was he correctly de-listed if valve reversed it? It was a bug. The problem was that valve changed it so the tag doesn't get set immediately. Running a plugin like that is fine but you need to monitor the tags to make sure they get set. No de-listing happened since then and more servers are bringing it back.
You just can not rely on the built in function anymore to avoid de-listing, you NEED to make sure the tags are set immediately and you will be OK. Like valve said, it would be "straying into the grey area" for them to de-list such servers and they re-listed the ones they got last time due to that bug. On Fri, Apr 12, 2013 at 3:11 PM, dan <[email protected]> wrote: > On 04/04/2013 06:41, Essay Tew Phaun wrote: > >> Now can you finally put that other thread to rest and admit you were >> wrong? >> The servers that didn't have their tags updated were mistakenly delisted. >> I >> don't know how anyone can have a conversation with you if you can't even >> read and comprehend what Fletcher point blank said. >> > > You were correctly delisted and the plugin you used that caused the > delisting no longer exists on your server. > > if you're still unsure of that, put the plugin back and see what happens > to your servers. > > As I said, the relevance to this thread is that you squealed like a stuck > pig when you were taken to task and now you're suggesting they delist > others. > > If you want good features stop abusing them. You cannot moan about Valve > removing features that are abused when you abused them yourself. > > -- > Dan. > > > > ______________________________**_________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.**com/cgi-bin/mailman/listinfo/**hlds_linux<https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux> > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
