Announcement

Collapse
No announcement yet.

Introduction and a little help needed

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Introduction and a little help needed

    I didn't want sound needy and immediately ask for help, so figured I'd introduce myself first.

    Veteran of Quake since release and a love affair with anything id Software. Miss the simplicity of being a teenager and able to stay out late at LANs with friends and Quake until the sun comes up.

    I also want to thank those who made ProQuake and who put their time and effort into it; it's exactly what I was looking for. Tried the other well-made engines but the GLquake look just feels right.

    All gushing aside, here's my problem. I'm trying to connect to a server, but it is not allowing me to. Here's what it says:

    Syntax: connect server:port (port is optional)
    host_error: connect failed

    I'm able to connect to a server on EZQuake without an issue. But as stated above, I'd much rather use ProQuake. I did a Google search and found a thread of someone with the same issue, but that was a few years ago, so not sure what the resolution was.

  • #2
    EzQuake is a QuakeWORLD client, ProQuake is a netQuake client.
    The two engines 'speak' a different protocol, and are not interchangeable.
    If you want that basic glQuake look and allowed to play on both QW and NQ try ZQuake; you can connect to nq servers using /nqconnect quake.server.com:26000 or qw servers using /connect quake.server.com:27500
    www.quakeone.com/qrack | www.quakeone.com/cax| http://en.twitch.tv/sputnikutah

    Comment


    • #3
      26000 to 26015 are for NetQuake (ProQuake etc.)
      27000 to ... are for QuakeWolrd (EZQuake etc.)

      Comment


      • #4
        1: the protocol is not the same (thus they cannot connect to the same server).
        2: they use different ports (the address bit after after the colon, you can use this as a hint to the server type, but only a hint).
        3: NQ engines (including proquake - ie: winquake/glquake rather than (sw)quakeworld/glquakeworld) have certain issues with computers with multiple IPs, and servers which have any sort of firewall/nat infront of them.
        Some Game Thing

        Comment


        • #5
          ^fte can also connect to both
          i was going to port nqconnect to ezquake from zquake
          (i got 90% there then all the ezq devs bitched that it was superfluous so i stopped)
          www.quakeone.com/qrack | www.quakeone.com/cax| http://en.twitch.tv/sputnikutah

          Comment


          • #6
            Awesome, thanks for the clarifications.

            Making this the weekend project. Got Windows 8 and time for the brutal part of data backup.

            Comment


            • #7
              Weekend project?

              Data backup?

              All you have to do is type "connect (proper server address)" in the console of a compatible client - which should take about 1 second.

              edit: oh wait, I think I get it, you are also upgrading to Win8? You should back up your files, as you create them, to somewhere remote (the cloud, usb stick, external drive, etc).

              Waiting til you are ready to crash your OS is a really dumb time to start. What if you had a hardware/OS malfunction before you were ready?

              I backup to all of the methods I stated.
              Last edited by MadGypsy; 02-23-2013, 07:02 AM.
              http://www.nextgenquake.com

              Comment

              Working...
              X