Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Neonivek]

Plenty of religions have their sacred meteorites. The Black Stone in the Islamic Kaaba at Mecca is one such stone, visiting it is the key point of the pilgrimage. The Roman Emperor Heliogabalus castrated himself to join the cult of a meteorite that looked like Diana, Goddess of the Hunt. There's quite a few Hindu ones as well. This might work well in the Religions and Temples thread.

Plus some religions even had explanations of where Meteorites came from.

[Aspgren]

Randomly cause cave ins and kill dwarves? Not good.

Creating meteor impact sites during worldgen? Very good!

Give a warning in fortress mode "a meteorite is heading for this area!" and pausing, giving you a short while to get all dwarves indoors? Sounds fun, as long as you don't create any armageddon type meteors..

[Neonivek]

Randomly cause cave ins and kill dwarves? Not good.

Creating meteor impact sites during worldgen? Very good!

Give a warning in fortress mode "a meteorite is heading for this area!" and pausing, giving you a short while to get all dwarves indoors? Sounds fun, as long as you don't create any armageddon type meteors..

The Vast majority of them are rather small... It would be a stone's size in game. It is rather unlikely to actually strike a Dwarf. (REALLY small in real life. The vast majority of them are like grains of rice)

[penguinofhonor]

I want the Blob to come out of impact sites occasionally.

[b1gb0y2013]

Maybe religion could tie in with this?? (I heard that religion might become more in the game) That if you know your deity is getting pissed off, you should be getting ready for meteors

[612DwarfAvenue]

It's be pretty cool if they were in worldgen. If they're also in actual gameplay, i agree with what Aspgren said. Like, pause, give a warning that it's coming, and zoom to the spot where it's gonna hit. Init options to turn them off in gameplay, and worldgen options to control what happens. (maybe even have different types in the raws so you can have Iron meteors, falling chunks of !!HFS!!, etc.)

[RedWarrior0]

Init options to turn them off in gameplay, and worldgen options to control what happens. (maybe even have different types in the raws so you can have Iron meteors, falling chunks of !!HFS!!, etc.)

Absolutely for the first one. Worldgen has ridiculous amounts of control for EVERYTHING, so meteors would naturally be a part of that.

For the raw options, I have a basic outline, though.

Spoiler: Wall of text (click to show/hide)

In worldgen, you would have a few options:
Meteor frequency --0 to some really high number; 0 means no meteors, higher is more frequent.
Meteor size weight (minuscule) -- for meteors that leave very little trace besides craters; defaults fairly high
Meteor size weight (small) -- for meteors that are a tile or two; defaults medium-low
Meteor size weight (medium) -- typically 5-10 tiles of stuff; defaults low
Meteor size weight (large) -- the smallest that can contain items or life; defaults very low
Meteor size weight (huge) -- the stuff that can, with bad luck, wipe out a small fortress; defaults to almost nonexistant
Meteor size weight (apocalypse) -- craters that take up multiple region tiles, wipe out huge amounts of life, and will affect the climate of most of the world; defaults off
Meteor source -- this would be a single word (METEORGROUPNAME), used in meteor.txt, and makes the templates and adjusts things

In meteor.txt, you would make a template for the types of meteors:
[METEOR:METEORGROUPNAME]
[METEOR:MATERIALTYPE:MATERIALNAME:#:#:#:#:#:#:#] -- MATERIALTYPE is the descriptor for the class of material; the same thing as the first line of the material raw entry sans brackets; the first # is weight for that type of meteor being chosen (must be positive); the other #'s refer to individual weighting for size classes (-1 means it can't be that size); leaving out a # for the first and then the last six assumes it's 1 and 0, respectively.

After that, you would have the option of placing items and creatures. You would place a tag for each creature, with numbers for min and max of the number of creatures; you could also use DEMON, TITAN, and FORGOTTEN for those terrors. You would also define the items possible in much the same way as a custom creature with an item for a corpse, with optional weighting if you want it that way.

For the process, it would roll a 1d[arbitrarily large number] for the event occuring, another 1d[smaller number, but still arbitrary] for advance notice, then go to the referred meteor source. It would total the weightings for type of meteor in [METEOR:METEORGROUPNAME], then roll 1d[meteor type weighting total] for the type, then figure out size. It would add the meteor size weights from the worldgen to the respective size weights from [METEOR:METEORGROUPNAME] in meteor.txt for the effective meteor size weight, total those up, and roll to determine size. Then again for crater size and creature/item.

[TolyK]

yep