Jump to content

Roy

Banned
  • Posts

    2,853
  • Joined

  • Last visited

  • Days Won

    383

Posts posted by Roy

  1. I've tried querying the Master Server with the filters \appid\730\password\0, \appid\730\password\1, and \appid\730\nor\1\white\1\password\0 and it appears the password filter is just non-existent or not working anymore. So I couldn't get the amount of CS:GO password-protected servers for now. I will adjust my script to do a for loop and detect if the server has a password or not.

     

    I've also made a Youtube video of my current in-game server browser and as you can see, there are many password-protected servers along with empty servers:

     

     

    Thanks.

  2. 52 minutes ago, Eli said:

    I doubt the mode can handle 64 without it being a cluster fuck where people die instantly and have to wait forever till the round ends

     

    edit: it can handle it but it will be shit

    It'll be fine if custom maps are made designed for 64 players. The current map would definitely be too small for 64 players in my opinion.

     

    Thanks.

  3. And yes, I know I am crazy for even trying to get Valve to change anything community server-related considering Valve has only hurt community servers in the last few years (especially the servers that obeyed their guidelines unfortunately). However, as long as I'm in GFL and active, I'm going to try to push Valve to provide better support for community servers ;) 

     

    Thanks.

  4. All would depend on how this F2P change turns out for community servers.

     

    If we start getting population, I'm willing to open up servers in our UK location and even opening up an expansion in Asia or another location if wanted. OVH has pretty good machines in Singapore:

     

    24-12-06-2018-FAeVAGIB.png

     

    All depends on how everything turns out.

     

    I still want Valve to implement this change to the server browser, though... I would be very confident community servers would start receiving population if 3/4 of the list wasn't full of empty and password-protected servers.

     

    Thanks.

  5. Fixed

    • Increased a profile cover photo's opacity from 0.0001 (not visible) to 0.6 (visible).
    • Registration page throwing a template error.
    • Replaced the banner with an official GFL image from the website.

     

    Thanks.

  6. Updated/Fixed

    • Reinstalled and updated the Shoutbox to the latest version to fix the emoticons not inserting from the menu.

     

    Notes

    • The re-installation of the Shoutbox dropped and recreated all the tables related to it. I made a backup of the messages table beforehand so I could restore that. However, all client-side settings (e.g. the Shoutbox's height) have been reset to the default value (300px).

     

    If you find any issues, please let me know.

     

    Thanks.

     

  7. I don't recall there be any restrictions at the moment (through IPS 4 itself). However, if you do make it too long, you'll be asked to trim it down or at least put everything in spoilers using the spoiler tags. Users can disable user-specific signatures as well.

     

     

    When I get back, I might look into setting up official restrictions.

     

    Thanks.

  8. 11 hours ago, OxideTM said:

     

    C:\Windows\system32>tracert 216.52.148.47

    Tracing route to c-216-52-148-47.managed-ded.premium-chicago.nfoservers.com [216.52.148.47]
    over a maximum of 30 hops:

      1          8 ms        4 ms        5 ms       192.168.0.1
      2      118 ms        13 ms     32 ms       172.19.63.255
      3        10 ms        7 ms             *        202.163.100.85
      4         3 ms         3 ms       4 ms      202.163.100.66
      5         4 ms         3 ms        3 ms      119.159.240.53
      6         6 ms         5 ms        9 ms      khi77.pie.net.pk [221.120.251.205]
      7         9 ms         3 ms        5 ms      static.khi77.pie.net.pk [202.125.128.171]
      8     108 ms     108 ms    109 ms      te0-4-0-27.ccr21.mrs01.atlas.cogentco.com [149.14.126.1]
      9     108 ms       111 ms     114 ms      be3092.ccr41.par01.atlas.cogentco.com [130.117.49.153]
     10      116 ms      115 ms     116 ms      prs-b2-link.telia.net [213.155.141.226]
     11     224 ms     224 ms    235 ms     prs-bb3-link.telia.net [62.115.122.4]
     12     222 ms           *                  *        nyk-bb3-link.telia.net [213.155.135.5]
     13     237 ms     238 ms    240 ms    nyk-bb4-link.telia.net [62.115.142.222]
     14     218 ms     224 ms     217 ms    det-b1-link.telia.net [62.115.113.35]
     15      221 ms      221 ms     221 ms    chi-b21-link.telia.net [62.115.141.222]
     16    248 ms     240 ms    238 ms    chi-b22-link.telia.net [62.115.141.170]
     17            *                *                *          Request timed out.
     18            *                *                *          Request timed out.
     19            *                *                *          Request timed out.
     20           *                *                *          Request timed out.
     21            *                *                *          Request timed out.
     22           *                *                *          Request timed out.
     23           *                *                *          Request timed out.
     24           *                *                *          Request timed out.
     25           *                *                *          Request timed out.
     26           *                *                *          Request timed out.
     27           *                *                *          Request timed out.
     28           *                *                *          Request timed out.
     29           *                *                *          Request timed out.
     30           *                *                *          Request timed out.

    Trace complete.

     

     

    C:\Windows\system32>ping 74.91.119.54

    Pinging 74.91.119.54 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 74.91.119.54

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

     

     

    I haven't done a scan till now but I will perform one today over night and wil let you know the results. However, I have just performed a clean installation of windows last week and till then I haven't done any unusual online activity or connected any external storage with my laptop so I highly doubt I'll have anything fishy in my computer.

     

    Just as I said, everything happened over night. I was playing over an NFO hosted server whose IP I will communicate if you want here. I disconnected from the server. Shut down the computer. Went to sleep. The other day I tried connecting, I saw the server's status as not responding. I tried accessing that community's site and still couldn't access to it till date. Not with my current internet connection.

     

    One more thing I might add here is that I had a similar issue like this before 2015. I couldn't connect to nfo servers at that place. I contacted NFO's technical staff and didn't get a satisfying response. I think I met Soja or you there as well when I referred GFL's CSS ZE server back then. Back then, I was able to access NFO's site. Now, I can't even access NFO's site. Their page is not even opening so that I may file a complaint.

    No idea what happened in a matter of days. Is it possible that my windows might be blocked my access to NFO as whole. If that's the case, can I be assisted in this matter like where to check? etc.

     

    Adding further, I can't access NFO from my mobile phone as well (same network)
     

    Thank you for those results.

     

    From the looks of it, either NFO/Internap is blocking your connection or your ISP/network is blocking connections to NFO/Internap servers. Considering it's timing out after getting to a hop in Chicago (where the server is located).

     

    I will be creating a ticket with NFO to confirm. I will also be performing a trace route from the server to your IP address to see if I can gain additional information.

     

    I'm glad you were able perform a virus/malware scan on your computer. Though, it is possible another device including the router/modem itself could be performing port scans. This is assuming that NFO/Internap is blocking your IP for ports scans. We won't know until it's confirmed on their end.

     

    From the sounds of it, your computer wouldn't be blocking the connection. It's possible your router/modem could be blocking the connection. Though, it all depends on the type of router/modem you have. I'd say log into the admin portal and see if you can find a section with blocked hosts. Sadly, I don't believe this'll help because you appear to be unable to connect to any NFO/Internap servers in Chicago.

     

    I will create the ticket either tonight or early tomorrow.

     

    P.S. Sorry for any grammar mistakes, really tired right now lol.

     

    Thanks.

×
×
  • Create New...