The Ur-Quan Masters Discussion Forum

Hi, all!

I'm trying to add earthlings to the galaxy and have managed to
-edit the sphere of influence
-edit their encounter probability

I got the cruisers to appear in interplanetary and hyperspace although I just linked their conversation to supox conversation in races.h file.
#define RACE_COMMUNICATION \
      SUPOX_CONVERSATION,       /* (HUMAN_SHIP) */ \

So they are earthling cruisers when in IP and hyperspace and in battle too, but the comms are for supox.
But, of course I want more than this :D

So, to make new human comms possible I copied the comm/supox dir and made it comm/human, editing the variable names accordingly.
Then I changed the races.h to define RACE_COMMUNICATION/HUMAN_CONVERSATION
and put a new switch case to commglue.c for HUMAN_CONVERSATION.

Here's the problem: all the *_CONVERSATIONS are defined in ires_ind.h, which gives some mystical (memory addresses??) for each one, like
#define SLYLANDRO_CONVERSATION 0x16a02907L
#define UMGAH_CONVERSATION 0x16c02a07L
#define URQUAN_CONVERSATION 0x16e02b07L

Now what the dang should I put as the HUMAN_CONVERSATION address?
Is this btw only for the OSX build or is the same ires_ind.h there for all the other systems too? This is baffling.

I read
http://forum.uqm.stack.nl/index.php?topic=4439.0
but it wasn't specific enough to help me...

They are not memory addresses. They are resource identifiers. Their format is described in doc/devel/resources.

But I suggest that you base your mod on the subversion version of the source. Those resource identifiers are gone, and a more human-friendly system is in place.

Thanks a bunch!
It really would be helpful not having to mess around with those identifiers...

Sorry for my utter stupidity, but what exactly is the subversion version?  :P I'm currently compiling from the 0.6.2 source tar.gz.

Hmm, hehh...
Found the subversion repository at http://uqm.stack.nl/files/snapshots/  ;D

Do the content files also need updating? At least the old graphic contents don't work anymore,
I get these all over the place:
Trying to get undefined resource 'ship.arilou.code'
dummy.c::CaptureCodeRes() hCode==NULL! FATAL!

Subversion (SVN) is a version control system (like CVS — maybe you've heard of that). It makes it easy to keep track of old versions and merge in changes. The SVN repository is where the ongoing development takes place.

The content is indeed heavily modified. To keep your development synchronised with the latest changes, you're better off checking out everything from the SVN repository, rather than working with those snapshots.

You need a Subversion client. On *nix systems, there's a command-line client called simply "svn". On Windows, most people seem satisfied with TortoiseSVN.
On *nix, you run "svn co https://sc2.svn.sourceforge.net/svnroot/sc2 sc2" to check out the UQM source. Using TortoiseSVN, I don't recall exactly, but you would specify "https://sc2.svn.sourceforge.net/svnroot/sc2" as the repository to check out.
You may want to read through a Subversion introduction for the other svn commands.

<------------uses TortoiseSVN for his mod. Seems to do the business!

Luckily, the svn command line tool is featured also on Mac OS X, so I used it.

At first I was aghast: Trying to run the new, (sub)version of UQM from terminal, all the keyboard input was directed to the terminal window instead of UQM application. However it is no problem: Clicking the icon starts UQM just fine!

(In the 0.6.2 source code clicking the icon just crashed UQM and it had to be run from terminal at least on my OSX.)

Hey, could you tell me how to permanently change the install config options? I'd like to have the joystick disabled permanently since I've got no joystick and when doing the "CFLAGS="-I/Library/Frameworks/SDL.framework/Headers"  ./build.sh uqm config" thing I have to disable the joystick every time. A small, but definite annoyance :)

As long as you don't delete the config.state file, the build configuration options should remain as they were.

It seems that compiling in OSX is picky: If I try to build install without running the build config with CFLAGs, it won't find the SDL headers, even if the config.state is there already. So I need to run the config each time.

But perhaps I'll cook up some way to add the CFLAGs permanently or make my command line compilation script type those 7 and 2 to disable joystick, so it's no biggie.

Hehh, changing build.config file in build/unix did the trick, now the joystick is disabled by default.

I can clean, config, compile and run with two keystrokes now. Oh, the joy, elation, rapture, delectation plus happy days and jubilation.