> I am a fan of STK and would like to contribute my admittedly modest
> programming skills to help make it an even better game.
Great - welcome!
> I have been reading the source code to become familiar with how STK is
> put together and have also had a go at fixing bug 1812296 (AI has great
> trouble with the bridge on the star track). I have attached a patch for
> startrack.drvr which fixes this bug by moving the right driveline so the
> AI karts do not get stuck in the wall and repeatedly rescued.
Well done - I leave this for Coz to have a look at, he's the export on
> While reading the code, I think I found another bug: in main.cpp, the
> code for the --list-karts argument has the comment "// --list-karts
> seems to need a drv_init() ???" and then drv_init() is called (line
> 201). There is no subsequent call to drv_deinit(). When running
> --list-karts on my system with STK in fullscreen mode, this causes the
> display resolution to be fixed at STK's resolution after --list-karts
> has run. To fix this, drv_deinit() needs to be called at the end of the
> if block, or the drv_init() call needs to be removed (I compiled STK
> with the function call commented out and --list-karts ran fine, so I
> don't know why it is needed, is it a portability issue?)
And I'll have a look at this - most likely the comment is outdated (by
some other changes in between) by now, so the call should just be removed.
> Anyway, I hope I can help out somewhere. Is the TODO list on the wiki
> up to date or can you think of any other (small?) coding jobs for me to
> get started with??
Well, I intend to update the todo list soon :) We have a new web/wiki
master, so I'll have to synchronise this with him. But I think at least a
few items on the todo list are outdated.
What you should start with: subscribe to at least supertuxkart-devel, probably
to supertuxkart-commit as well. The first one guarantees that you are up to
date with our discussions, the second one will tell you what commits are being
done, and that makes sure that you always have the latest version of the sources.
What platform are you actually on (Linux, windows, Max)?
What you can have a look at:
1) some bugs in the sourceforge bug tracker (if it's assigned to someone, you
could just post here on the list if you want to handle this, since esp. at the
moment people are rather busy and might be happy with someone taking over a
I am currently working on the new physics, so I'll guess for now leave those
bugs best to me (unless you want to get involved with the bullet physics
code, there's a lot of work here :) )
2) some small items from the todo list, which are not being worked on:
- let's kart in a grand prix start in order of points (e.g. the karts with
the most points goes first). This should be made a big flexible, since
some people suggested to do the opposite: most points goes last.
So you could add a flag to the stk_config file, which would select
the kart's start order. This way people without programming skills (like
a lot of the play testers) can easily change the behaviour of STK.
In the end we should let the playtesters decide what's best :)
- add a menu to select screen resolution
- write all warnings into a file, instead of stderr (or better: both).
We have a lot of problems with bug reports by people who are using
a laucher (on Macs), and they don't see any warnings or error messages,
and quite often don't even know how to start STK from a terminal.
So being able to tell them: 'send me the file ...' would be a huge
3) Some other items I am thinking of adding:
- add a kid of 'theme' (like the halloween theme): this would allow
people to select a theme from a menu (and/or command line), which would
change background image, models for herrings, music, ...
That hasn't really been discussed yet, if you are interested, we should
set up a wiki page first. Themes could be: Halloween, Xmas, Easter,
... or perhaps: heavy metal (music instruments as models, different music)
Most of this (like herring models, different music) is already implemented,
it should just be done consistently under one 'wrapper' (or 'controller').
- A bigger job would be to implement a kind of 'unlock' system: a player
would have to fulfill a certain task (say finish a track in a certain
number of seconds), to unlock additional tracks, characters, ...
Or have a look at the game design page, in which suggestions from very many
people are collected ... totally unsorted at the moment :) If you want to
do some of these suggestions, please discuss this on the list first, since
the suggestions are not really 'approved' - gee, that sounds strict - I mean
that often people suggest things they have seen in other games, or an item that
might be too powerful. Our goal is to come up with some new ideas - we would
prefer to make STK a game on its own, and not just a copy :) I hope that we can
get the todo list/milestone page and game-design page up to date soon (see my
hopefully soon to come other posting).
Generally: what would you be most interested in? That would probably be more
important :) We could probably divide some tasks in smaller bits as well,
so that more people can work on it, and/or make it more manageable.
Hope that helps!