strata, on 07 August 2012 - 11:36 PM, said:
Ick. It's a lot of change for no reason. What if you adjust one info string so it says you use SACC without changing all of that stuff?
Can you not do all of the printf -> dprintf and PRINT_ALL -> PRINT_DEVELOPER stuff? IIRC that's in the official client too but it's just churn. If you want to maintain a fork of ioquake3, you don't want trivial changes like that making your life difficult. Smaller diff is better.
strata, on 07 August 2012 - 11:36 PM, said:
What's your plan for updating if you didn't fork it from an upstream ioquake3? :)
You could base it off of my ioquake3_mirror if you want the latest updates. There's no good solution because I may leave the UrT scene and miss changes. You could of course create your own ioquake3_mirror against their SVN but then you would have the same annoyance that I have with keeping it up to date. It would be best if the ioquake3 project either switched to mercurial or git or had an official mirror so you could trust it.
I would volunteer to help you but my UrT journey ends with 4.x. I just looked at their Sys_StartProcess...