Official ZBlock Integration with Source?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • FlyingMongoose

    #16
    DevgruSeal H.E wrote..

    But joining a server, not knowing anything about the server, and the server not having any MOTDs saying, "We'll abuse you for no reason whatsoever. We'll kick you for no reason whatsoever!" shouldn't warrant config abuse.
    What exactly do you mean by config abuse?



    Do you mean administrators forcing cvars on you?



    When it comes to exploitable cvars, I'd say that's well within the range of what admins should be able to enforce, however, if it's an admin running a command on the client (example +left so you keep turning left) then it should be blocked

    Comment

    • DevgruSeal H.E

      #17
      FlyingMongoose wrote..

      What exactly do you mean by config abuse?



      Do you mean administrators forcing cvars on you?



      When it comes to exploitable cvars, I'd say that's well within the range of what admins should be able to enforce, however, if it's an admin running a command on the client (example +left so you keep turning left) then it should be blocked
      That's the abuse I was talking about. Or forcing fps_max 5.

      Comment

      • FlyingMongoose

        #18
        Edited by [user="59887"] @ [time="1164479823"]

        Okay you're talking about admins enforcing cvars to the point of their exploitable potential, not "fixing" them. Because that's what I do sometimes, I fix them so there's performance increase, and less issues between the player, other players, and the sever.



        No, not everyohe uses 56k anymore is true, however, my clan has 1 member that has 56k because he actually can't get cable or DSL where he lives. However, he doesn't lag, ping spike, or slingshot like those who don't know how to set themselves up properly. That right there is proof that most instances of the net code nowadays (when it comes to lag anyway) works at least a little bit. He's as smooth as any high bandwidth user with a ping above 200. There's no registration drop or increase either, always consistent.

        Comment

        • DevgruSeal H.E

          #19
          He's an advanced user. He knows what to set his rates to. But most 56kers don't.

          Comment

          • Zips

            #20
            Same can be said about broadband users as well. Some 56kers don't know, some broadband users don't know.

            Comment

            • FlyingMongoose

              #21
              Well we shouldn't be kicking people for their connection, we should assist them in setting their rates properly, if they end up being ass-hats THEN we should kick them.



              My best rates for good registration and response to chicago servers: cmdrate 65, updaterate 100, and rate 20000-25000. But that's just me, I live about 4 hours from chicago, and a tracert tot he chicago server I play in shows 10 hops.

              My internet connection is 5 mb/s down. And 512 kb/s up.

              Which is why cmdrate is less than my updaterate (also why I believe they shouldn't be put into the same command, because 100/100/30000 isn't the best setup).

              Comment

              • FLeK0

                #22
                Even a 256/128k down/up connection can handle 101/101 rates without lagspikes. Valve should change steams requirement from "internet connection" to "broadband internet connection", and force the rates up to at least 60/60.

                Comment

                • m4elite

                  #23
                  Everyone in every pub I go into 1.6 or cs:s has default rates, all they do is bitch about registration.. when they don't know they have crappy rates and interp all the shots they get, valve needs to add rate configuration into the gui near keyboard customization..

                  Also, the min and max rate settings a server allows should be told to you when you connect to a server.

                  Comment

                  • FlyingMongoose

                    #24
                    FLeK0 wrote..

                    Even a 256/128k down/up connection can handle 101/101 rates without lagspikes. Valve should change steams requirement from "internet connection" to "broadband internet connection", and force the rates up to at least 60/60.
                    Lagspikes yes it can handle fine like that, however consistent registry it does not handle properly without the rates I have set.



                    Something a lot of people still don't realize is they actually DID fix one problem with the rates a long time ago: 101 is NOT necessary to force true 100 anymore, just 100 is, most cvar-consistency plugings enforce it to 100. If you think when it changes it changes your performance you've got a screw loose.



                    Note: there are plenty of formulas that can be used to modify rates for proper settings out there. Some of which are in rate calculators. A while back (before that fix I mentioned above was done) i even made one in PHP. I've been looking at maybe bringing it back. But I haven't had the time. It's a simple rate calculator, I based it on the old HLToolz app's formula.



                    I'll tell you what cvar-x forces by defaults

                    updaterate: 30-100

                    cmdrate: 20-100

                    rate: 5000-30000



                    plenty of other cvar enforcement plugins are at least close.

                    Comment

                    • V1P3R

                      #25
                      Yet another classic example of Valve doing things that don't really matter when there are much bigger issues that need to be addressed.

                      Comment

                      • LeRaldo

                        #26
                        Zips wrote..

                        Because they're working with the community to please the community?
                        Because they're giving moronic admins an easier way of forcing terrible rates on people. I'll admit that some CVARs need to be restricted, but cmdrate and updaterate need to stay as they are.

                        Comment

                        • peagle

                          #27
                          V1P3R wrote..

                          Yet another classic example of Valve doing things that don't really matter when there are much bigger issues that need to be addressed.
                          Another classic example of someone commenting on issues addressed through PR, whilst assuming none of the issues you are interested in are being processed.

                          Comment

                          • FlyingMongoose

                            #28
                            LeRaldo wrote..

                            Because they're giving moronic admins an easier way of forcing terrible rates on people. I'll admit that some CVARs need to be restricted, but cmdrate and updaterate need to stay as they are.
                            What exactly are "good" rates to you?

                            And not all admins are morons. I generally try to assist people in setting their rates properly.



                            I base my rates on pings using the windows ping command, tracerts, download and upload speed, and even type of connection (dsl, cable, and fiber). I also sometimes run tracerts to see how many hops there are between me and the server I'm playing on as well as the ping on each hop.



                            Though MOST of the time: My optimal rates, are 100 updaterate 65 cmdrate, and rate of 25000.



                            But that's just me.



                            The funny thing is: With a rate setup like that, on (most) chicago servers the window that shows scores says my ping is 15, whereas my net_graph shows 30-40. But I've heard no complaints of slingshotting, skipping, or lag spiking on me...ever.



                            And yes, I get a major registration differents at 100/100/30000(or 25000) vs 100/65/30000(or 25000). Some people don't claim to notice it. But I do, and can.

                            Comment

                            • Thortok2000

                              #29
                              peagle wrote..

                              Another classic example of someone commenting on issues addressed through PR, whilst assuming none of the issues you are interested in are being processed.
                              Where exactly do we get information on the 'processing' of issues we're interested in?



                              Getting information on any issues we're interested in at all is rare, which is why I applauded this information.



                              I'm not assuming that the issues I'm interested in aren't being worked on, I'd just like to know what's up, what's taking so long, that they ARE being worked on, etc.

                              Comment

                              • entRo

                                #30
                                peagle wrote..

                                Another classic example of someone commenting on issues addressed through PR, whilst assuming none of the issues you are interested in are being processed.
                                You'd think if they were actually going to fix bugs that have been around for years, they'd maybe.. say so. Just a guess.

                                Comment

                                Working...