Modding Questions

[Fingers]

In Windows, the command line options can be added to the target line in the shortcut. Right-click on the shortcut to Weird Worlds, select "properties", then "shortcut" tab. In the "Target" field you'll see the path to weird.exe. Just add any command line options to the end of the line, separated by spaces.

When working on a mod, you might want to make a new shortcut with options like: -game yourmodname -skiplauncher -verbose . This will make it launch your mod without having to select it in the launcher.

The -verbose option makes the game print out a lot more debug info into the stdout.txt that's in your Weird Worlds folder.

The MIRROR label seems to have been left behind when I moved text into the strings.ini. Sorry

The color tags in text are simply RGB, where the value for each component varies from 0 to 9. E.g. 900 would be bright red, while 090 would be bright green.

Devices only use PAGE entries.

The movement speeds in general are in metres/second while turning speeds are in degrees/second.

In the case of starship hulls, the MOVE parameter is the speed in m/s when using a thruster whose PAR0 is 100 (ie. Fusion Tube). The TURN speed is similarly affected by the thruster... Basically the thruster strength is like a percentage of the movement or turn speed. When you use a Reactionless Thruster with strength of 210, the ship moves and turns over twice as fast as defined in the hull file.

[PaddirN]

I noticed in the kawangi and ravian hull files under one of the weapons there were some flags after the xy coordinates: 'hidden' 'nouse' 'trigburn'/'trigblow'. I assume these are fairly self explanatory, but are there any other flags? And also I was having problems in making a ship explosion that does damage to everything around it like the wp_kawangiblow. I want to keep the same idea, but use a different visual effect for it (a shockwave). I've been messing around with it for a few hours and its driving me crazy. These particle effects just confuse me for some reason.

[Fingers]

The weapon system flags are:
hidden - not shown in displays, can't install/uninstall
nouse - not used except when triggered by following flags
trigkill - trigger when the ship starts to burn
trigburn - trigger continuously while burning
trigblow - trigger when it stops burning and explodes

The way I'd do a shockwave-like death effect is similar to the Tchorak missile explosions... Make it shoot many small projectiles with a 360-degree spread, and use a single shockwave particle (like the one used for gauss cannon impacts) as a "muzzle flash". Note that this won't do damage to any friendly ships.

[PaddirN]

Aight, broke the cardinal rule and added a few things at a time before I checked...

getting an error whenever I explore a planet, found this in the stderr.txt file:

Fatal signal: Segmentation Fault (SDL Parachute Deployed)

not exactly sure what that means, would the stdout.txt file have more info?

[PaddirN]

Oh, and before I forget,

is it possible to make a weapon that fires, explodes at a certain distance (a la the multi-missile), and releases a swarm of fighters instead of missiles?

I'm thinking of the way the ravian debris work, though I'm guessing it's quite a different effect since this wouldn't be a trigburn or trigblow effect.

[PaddirN]

Here's the stdout.txt file if it helps

[Phlagm]

I think the stderr.txt file would be of more use. It's generally where I look. I had a similar problem the other day with a credits.ini overflow. Most things, (like # particles in weapons) seem to just stop loading at some point if you overload them. I spent a long time looking for that error with the credits.ini. My suggestion would be to remember every seemingly silly thing you altered (credits.ini crashed the game only when I tried to fire up a simulator or a game, but not on the intro screen) and then look in the Engine Limitation on The Modmaker's Guide: http://www.digital-eel.com/modguide/engine_limits.htm
This is, at least, a start.

Also if you're having problems with the particle effects, the way I got my brain around them was to start with a weapon I wanted to make, and then strip out all the EMIT bits from the template weapon, leaving only the initial projectile part and its sprite. Then add more in one at a time.

I am not the expert on this, but I don't know of any way to load fighters without a fighterbay. If you figure out that there is a way, tell me about it. I could use it. YOu can do the following (which is in a weapon I have in my mod, but don't plan to release): Essentially make a version of the particle vortex cannon, only limit its firing arc, set it to homing, shut off spin, and replace the beam with a gun. It works well in some respects. YOu can make a drone that will turn and run down point defense rather well, and go up against fighters. The downsides are these: If you make it shootable, it'll last 3 seconds (though you can make it shootable, and make the target something really small SIZE 3 for example) because it can only endure one hit from anything. If you don't make it shootable, it's less realistic, but it'll gain you some fighter time. The next problem is more serious, though. If you don't make it "nocollision" it will fly straight to a cap ship and crack on its hull. Putting nocollision on them seems to defeat the point to me. You can stall this with prefpdef and preffter, but that will only buy you so much time.

-Jeremy

[PaddirN]

Well after poking around a little bit and examining the engine limitations I found that the max number of quests is 64, and apparently I had reached that limit... I think. Is that 64 quests listed in the game.ini file or is that 64 quests actually activated in a real game, because quite a few of the quests I have include KEYS with them that make them mutually exclusive, so I shouldn't think I would've reached the 64 quest max.

Whatever the case may be, after I took out a quest or two from the game.ini file it started working again.

[sgqwonkian]

Does anyone know if there's an equivalent to -verbose for Mac? I keep getting crashes, and it's a pain in the butt trying to figure out what's creating them.