Jump to content

Raz0r

Members
  • Posts

    1,135
  • Joined

  • Last visited

Everything posted by Raz0r

  1. You could run the JA server in a named screen session, set up an hourly cronjob and pipe to stdin of that screen (i.e. invoke screen with the -X switch) Apart from that, I'm not sure what can be done with JA+ With JA++, you could quite easily set up a Lua plugin to broadcast a message every x seconds, among many other things. EDIT: I suppose you could also rely on an external RCON method, i.e. running a php script or java app to send an rcon packet on a timer. I think JAWA currently does something like that. @@SiLink?
  2. *tips fedora*
  3. I believe the cvar has a different name in ioq3/rend2
  4. JO uses the same method as JA. JA+ uses fast HTTP downloads, which can also be added to JK2, but probably not by a QVM mod.
  5. The error appears to be in OpenAL. @@ent any ideas?
  6. It may be running an incredibly outdated version of JA++ (according to the credits) in which case you probably won't be able to run a listen server (aka /devmap) or use OpenJK with it, unless you upgrade to the latest JA++
  7. No http://www.youtube.com/watch?v=pDvPAMQ5r7w
  8. No one really succeeded, and it's far more secure than it was back then (in 2012)
  9. And strafe pads.
  10. What mod were you running, and were downloads enabled? Did you have a very secure RCON password? EDIT: I'm aware of a gamecode bug (memory corruption) when NPCs are around (i.e. SP maps) which will overwrite certain values, generally resulting in bots endlessly coming in. It's possible the clantag also got corrupted. Are you running JA+? The bug is fixed in OpenJK gamecode and JA++
  11. I believe it's only hardcoded.
  12. Well most of the code was already there =p here is what I did.
  13. CompJA Quake Live TDM team =p
  14. Reminds me of this =p
  15. If there were too many cvars, I'm sure it would have been an ingame error and your settings reverted. It was likely something else in that folder causing issues (outdated DLLs, invalid cvar setting)
  16. Perhaps the community perpetuating false information to justify their purist choices.
  17. And future-proof JA in-case Activision pulls the plug on their master server, or accidentally take it down and say it's for maintenance.
  18. SSE is not enabled by default, and as Ensiform said it must still adhere to IEEE floating point specification. I've still yet to see a demo in identical scenarios between base and mods with the same configuration producing different results.
  19. ^Which is fixed if you use OpenJK.
  20. Still OJP basic for now.
  21. No love for me? brb offing myself Ohwait no one actually cares about silly kids like you.
  22. Not much. Fixed some crashes, cleaned some things up. We planned on redoing it down the track when OJK was more stable.
  23. It would be server-side.
×
×
  • Create New...