This is one benefit, but I was mainly planning on releasing a plugin that allows other plugins to determine a client's MOTD state. For instance, if a client types a chat trigger to open your community's website, you could determine that they've joined via Quickplay and print the URL to chat instead.
N-Gon is correct in that none of my servers run ads (I got rid of Pinion shortly before they implemented the forced waiting timer). It would certainly be good to know how effective Quickplay is, and this is one way to do it. Doctor McKay http://www.doctormckay.com [email protected] On Sun, Jun 16, 2013 at 3:51 PM, N-Gon <[email protected]> wrote: > I've played on his servers, no Ads. Some of you can be so negative. > He probably just wants to see how useful/efficient Quickplay is, or how > many of his clients join from the Server Menu or Favorites > > > On Sun, Jun 16, 2013 at 3:49 PM, Ross Bemrose <[email protected]> wrote: > >> Question: Why do you need to know that information? >> Answer: You don't... unless you plan on doing things like blocking >> players that can't view your ads or some other such nonsense. >> >> >> On 6/16/2013 3:48 PM, N-Gon wrote: >> >> How is that annoying? What he wants to do doesn't affect the client in >> any way, it just let's him know which join from Quickplay and which >> didn't... >> >> >> On Sun, Jun 16, 2013 at 3:45 PM, Ross Bemrose <[email protected]>wrote: >> >>> So... you want them to fix a bug to stop annoying things... and in >>> doing so allow you to do completely different annoying things? >>> >>> On 6/16/2013 3:41 PM, Doctor McKay wrote: >>> >>> The problem is, many players are apparently incapable of pressing the >>> F7 button, which led Valve to cripple it in the first place. >>> >>> I mainly want Valve to prevent MOTDs from being loaded on Quickplay >>> clients so that I can detect if the client joined from Quickplay or not >>> (force the client to load a hidden page, then check if the page was >>> loaded). If there was some way to detect this, then I wouldn't necessarily >>> want this change to be made. >>> >>> As it stands, however, there is no way to determine whether or not a >>> client is able to view an MOTD window. >>> >>> >>> >>> Doctor McKay >>> http://www.doctormckay.com >>> [email protected] >>> >>> >>> On Sun, Jun 16, 2013 at 3:36 PM, Paul <[email protected]> wrote: >>> >>>> This idea would cripple functionality for radio on quickplay servers, >>>> just being one example of something it would further ruin for TF2 if such a >>>> restriction was imposed. I myself can't say I've come across servers like >>>> this, and if there are any then I imagine it's a mere handful (minor >>>> percentage of all QP servers). All players have to do in such instances of >>>> finding a server is just blacklist it and/or report it in-game, case >>>> closed. Alternatively if something is decided to be done in view of one >>>> complaint then disabling window.open would eliminate any new windows that >>>> you might be talking about even if that's the case. As I say, I haven't >>>> found this when going on servers myself. >>>> >>>> >>>> On 16 June 2013 20:19, Doctor McKay <[email protected]> wrote: >>>> >>>>> As I'm sure most are aware, a little while ago Valve changed the >>>>> TF2 MOTD panel so that it can't be reopened by the server if the client >>>>> joins via Quickplay (or using the matchmaking argument on the connect >>>>> command). However, this just prevents the MOTD panel itself from >>>>> redisplaying. The server can still open pages in the client's MOTD panel >>>>> in >>>>> the background. >>>>> >>>>> This means that the server can still spam traffic-to-cash URLs on >>>>> clients, many of which have noise-making Flash embedded or which open >>>>> popup >>>>> windows using JavaScript. In order to maintain the "sterile bubble" in >>>>> Quickplay, Valve might want to consider preventing servers from opening >>>>> webpages on Quickplay-joining clients entirely, not just preventing the >>>>> panel from being redisplayed. >>>>> >>>>> >>>>> >>>>> Doctor McKay >>>>> http://www.doctormckay.com >>>>> [email protected] >>>>> >>>>> _______________________________________________ >>>>> To unsubscribe, edit your list preferences, or view the list archives, >>>>> please visit: >>>>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> To unsubscribe, edit your list preferences, or view the list archives, >>>> please visit: >>>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >>>> >>>> >>> >>> >>> _______________________________________________ >>> To unsubscribe, edit your list preferences, or view the list archives, >>> please visit:https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >>> >>> >>> >>> _______________________________________________ >>> To unsubscribe, edit your list preferences, or view the list archives, >>> please visit: >>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >>> >>> >> >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit:https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >> >> >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds >> >> > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > >
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
