Announcement

Collapse
No announcement yet.

Not_in

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

  • Not_in

    Is it possible to figure out the engine and version being used and send that info to QC, in order to create flags like

    NOT_IN_DARKPLACES

    The reason I ask is, by gathering the engine version a switch/case could be used in QC to allow the proper code to run for the proper engine OR shut the code off completely should an engine not support it. This would only be helpful for arbitrary code that does simple things like rain, etc., but that would be enough to break some DP mods away from being DP only as well as allow for an alternate where an engine provides a certain function but differently than other engines.

    Consider this, Darkplaces and Qrack support rain, but differently. I made a weather entity for darkplaces and I could make one for Qrack as well. By having an engine version to check I could let the QC determine which weather entity to display (or none at all if it is another engine without that feature)
    Last edited by MadGypsy; 07-18-2012, 04:09 PM.
    http://www.nextgenquake.com

  • #2
    Unfortunately no. Definitely not in a legitimate way.

    QuakeC doesn't and isn't supposed to know things like what engine it is, but rather what the engine supports.

    Using QuakeC extension checks you can probably validate that an engine doesn't have, say, the DP Rain extension.

    I'm not Mr. QuakeC so couldn't tell you the specifics.
    Quakeone.com - Being exactly one-half good and one-half evil has advantages. When a portal opens to the antimatter universe, my opposite is just me with a goatee.

    So while you guys all have to fight your anti-matter counterparts, me and my evil twin will be drinking a beer laughing at you guys ...

    Comment


    • #3
      if you care enough to disable to support more than one mod, you'll likely not want to kick other engines that *do* support the things your mod uses back into the dark ages.

      in other words, detect things based upon engine features rather than the actual engine.
      the checkextension("EXTENSION NAME HERE") builtin is your friend.

      anything that explicitly checks for an explicit engine and version of said engine is a hack. that's fine if you're trying to side-step bugs in specific versions, but bad karma for anything and everything else.

      DP's rain is DP_TE_PARTICLERAIN.
      DP's snow is DP_TE_PARTICLESNOW.
      Some Game Thing

      Comment


      • #4
        woooha, jibberISH!

        Comment


        • #5
          checkextension("EXTENSION NAME HERE")
          Perfect, albeit a different method, this is exactly what I needed to know.

          Thank you
          http://www.nextgenquake.com

          Comment

          Working...
          X