Create an account


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Want to start helping with Xonotic code

#1
So I'm a beginning C programmer, but not a beginning programmer. I've been studying C for a while and I'm at the point where I think I can contribute to Xonotic in a (hopefully) useful way. I just finished this game as practice/experience coding in C:

http://www.jaynix.dyndns.org/files/SpacePong.zip
(Compiled for 32/64-bit Linux and Windows 32-bit. Source included.)

[Image: screenshotspacepong4.png]

Here's another example of my work: http://www.treeofvoices.dyndns.org

/shameless self promotion

I just had a few questions, about Git and some things to clear up first.

I'm not sure I understand how branching works/how I should go about editing/testing my code. Do I just create a new branch and start editing any of the the .C files and recompile to test? Is there any way I can accidentally fuck someone elses work up doing this (I'd like to avoid that)? Any other pointers/tips/things I should know/useful links you could throw at me to get me pointed in the right direction for making useful contributions? I'm new to open source/working on code that isn't my own :p
Reply

#2
C code is useful for the engine, darkplaces.
On IRC go to irc.anynet.org channel #darkplaces
Reply

#3
(03-19-2011, 12:24 AM)JayWalker Wrote: I'm not sure I understand how branching works/how I should go about editing/testing my code. Do I just create a new branch and start editing any of the the .C files and recompile to test?
Exactly.

(03-19-2011, 12:24 AM)JayWalker Wrote: Is there any way I can accidentally fuck someone elses work up doing this (I'd like to avoid that)?
As long as you're making changes in your own branch, no.
Links to my: SoundCloud and bandcamp accounts
Reply

#4
In this thread there are some helpful links and tipps, otherwise visit some IRC channels or read in the wiki Smile
Reply

#5
Hi. First, you might like to get write access to the repository. It will take some time for your request to get reviewed, but meanwhile you can start making local changes. Basically, you create a branch for each feature you implement. The branch name should start with your username followed by a slash, like so: jaywalker/feature, otherwise pushes will fail (so you can't accidentally screw up others' work, don't worry). When you change something on your branch, you simply recompile, test, and then commit your changes (git commit -a). To make your changes available publicly (assuming you have write access), you have to do a "git push". When you think your work is worth adding into Xonotic, you can request a merge with the web interface.


Also, you don't really have to know alot of C unless you want to screw with the engine, but it helps. The game code is writen in a special language called QuakeC, it is similar to C in syntax but is different in many aspects. Read this page for a quick reference.
Reply



Possibly Related Threads...
Thread Author Replies Views Last Post
  Random start weapons Lyberta 0 1,533 09-23-2017, 09:18 PM
Last Post: Lyberta
  Trying to understand darkplaces source code wiefie 37 7,477 09-22-2017, 01:37 PM
Last Post: Lyberta
  Altering Xonotic Source Code perljamz10 7 9,401 02-26-2013, 06:19 PM
Last Post: Mr. Bougo
  Planning to help with the code - where to start? Exitium 10 7,502 09-19-2011, 10:25 AM
Last Post: Lord Canistra
  Source code for the 0.1 preview release? twistedlincoln 4 5,910 01-03-2011, 09:18 AM
Last Post: twistedlincoln
  Darkplaces Code master[mind] 3 4,465 11-28-2010, 05:02 AM
Last Post: SavageX
Question [weapon name] is not available errors with no start weapons twistedlincoln 6 4,989 08-04-2010, 11:35 AM
Last Post: Roanoke
  editing nexiuz source code Jono 3 4,330 04-27-2010, 03:19 AM
Last Post: tZork

Forum Jump:


Users browsing this thread:
1 Guest(s)

Forum software by © MyBB original theme © iAndrew 2016, remixed by -z-