Conversation

Notices

  1. So I think L4D is trolling me now. Try compiling my map, it compiles. Try running it? TOO BAD (gives me an error I've never seen before). Goddamnit

    Monday, 02-Jul-12 09:31:04 UTC from web
    1. @widget I don't think it's a runtime error, it's something like "failed reading net_SignonState from loopback". I've only found one post dealing with it in my very brief search, and a solution wasn't found. Just... Aaaargh.

      Monday, 02-Jul-12 09:35:15 UTC from web
      1. @thunderdash It's a runtime error because it's not a compile-time error.

        Monday, 02-Jul-12 09:45:40 UTC from web
        1. @toksyuryel Oh, that's the difference? Huh, didn't know that. Cool :D

          Monday, 02-Jul-12 09:49:37 UTC from web
          1. @thunderdash It's called a runtime error because it happens when you try to run it. These are normally caused by passing faulty data to some function that wasn't expecting it (for example, the name being too long in your case). Compile-time errors are called such as they happen when compiling and are normally caused by actual errors in the code (frequently syntax errors, though often the actual syntax error won't be the same one the error is complaining about).

            Monday, 02-Jul-12 09:52:40 UTC from web
    2. @thunderdash OOOOOOOOMG I DON'T KNOW WHAT I DID BUT IT'S FINALLY WORKING

      Monday, 02-Jul-12 09:42:57 UTC from web
      1. @thunderdash *ahem* I think it was the map name being too long (I hit enter by mistake :D)

        Monday, 02-Jul-12 09:43:14 UTC from web