Yeah I'm fine with having to cache output from "status", but there are a few cases where "life updating" would be pretty nice to have, and we can't do that as often now!
How awful of an idea would it be to have status just repeat the last status until the timeout faded and you got a "new" status. (pretty bad but how bad?) On Mon, Oct 4, 2010 at 12:08 AM, Daniel Vogel <[email protected]> wrote: > It's quite annoying if you have to make a status screenshot for etf2l > matches, and the status command is not working. And it doesn't work on > both, client and server side... _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
