Print

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

[Kraiger]

Is there a convenient entity file lying around?

[Meph]

Hey, I just realized that overrides work for ammo in flight too. Dragondeplatino mentioned it.

So, you can have bullets and cannonballs flying around, instead of arrows, if you want to.

[zaporozhets]

Sorry for being inactive for a bit, personal circumstances led to a temporary progress halt and my laptop has been down for the count too. Also been waylaid by a nautical side project.
Blast mining is indeed being considered, though I'm leaning ATM towards it being a workshop that can be loaded with varying levels of explosive as I've no experience with levers (but thefriendlyhacker's explosive support is intriguing and ingenious).
Destruction function now has z-level support and variable explosive size (though not yet in a circle) so Vordak's ideas will be possible, could be similar to cannon rotation whereby it can be set to explode radially or directionally with a reaction.
Appreciate all the idea discussion, it's a great help.

Is there a convenient entity file lying around?

I'm afraid not, the mod has injected the appropriate entity stuff into the existing entity file(s) for a while now so people who didn't have any experience with modding could disable weapons they didn't like.
All the stuff is in text files in scripts/musket/entity/ and would need to be manually cobbled together. You could also use musket-settings to modify the existing entity file(s) and copy out the stuff you need.
I'm curious and I'd like to be of more help, what did you need it for?

[Grimlocke]

Alright, I got something presentable at last for both the ranged weapon script and the artillery script. Both are working as intended, I even got the organ gun to work satisfying. I ended up snubbing the job completion trigger entirely and just faking work completion timers with a timeout command, which lets me do some neat stuff like leading each organ gun barrel one by one with only one job set to repeat. It fetches some fairly basic properties per artillery type now, like rate of fire for multibarrel guns and reload times. It bases hitrate and reload rate on firer skill, a shoot force property the works exactly the same as vanilla ranged weapons and lets ranged-mod handle the remaining stuff like smoke and piercing effects. I still want to expand it a bit more to let me load them with stacks of ammunition rather than single items and add let the repeat jobs increase experience properly (and let botched job like a fire command that finds no ammo to fire NOT generate experience), but right now both scripts work well enough to let me finally update my main mod.

Pasties for ranged-mod and arty-mod respectively, more details in their -usage sections: https://pastebin.com/VZ0M5F6T https://pastebin.com/bq9kutS9

And a topic in the utils subforum: http://www.bay12forums.com/smf/index.php?topic=172239

[Fleeting Frames]

*looks around*

*sees this quite impressive thing*

Impressive!

The talk on explosive mining reminds me of dwarven power mining bug with sky support.

I'm an idiot, I didn't realize gas cannister liquids had to have the [SYN_CONTACT[ or [SYN_INHALED] tags for them to have any effect. Makes chemical weapons pretty useless when used with almost all of the native liquids.

I guess I'll eventually have to try and add some raws for new ones and a maybe a laboratory to make them in. There are plenty of effects to choose from, but deciding on names and reagents will be difficult.

About this...Since modding stone boiling points post-embark works, I wonder whether temporarily tagging the syndromes with that in df.global.world.raws on explosion would work.

Though one may consider it undesirable.

[zaporozhets]

Alright, I got something presentable at last for both the ranged weapon script and the artillery script. Both are working as intended, I even got the organ gun to work satisfying. I ended up snubbing the job completion trigger entirely and just faking work completion timers with a timeout command, which lets me do some neat stuff like leading each organ gun barrel one by one with only one job set to repeat. It fetches some fairly basic properties per artillery type now, like rate of fire for multibarrel guns and reload times. It bases hitrate and reload rate on firer skill, a shoot force property the works exactly the same as vanilla ranged weapons and lets ranged-mod handle the remaining stuff like smoke and piercing effects. I still want to expand it a bit more to let me load them with stacks of ammunition rather than single items and add let the repeat jobs increase experience properly (and let botched job like a fire command that finds no ammo to fire NOT generate experience), but right now both scripts work well enough to let me finally update my main mod.

Pasties for ranged-mod and arty-mod respectively, more details in their -usage sections: https://pastebin.com/VZ0M5F6T https://pastebin.com/bq9kutS9

And a topic in the utils subforum: http://www.bay12forums.com/smf/index.php?topic=172239

I had a quick look when it released and was very impressed with all the stuff you added (I'll need to take another look for the pseudo-completion timer stuff which I missed).
Wish I had the intelligence to make (or even use) modtool-style scripts but I find them very confusing to work with.
Not had much time to play with it in game yet though which is a shame, looking forward to seeing the organ gun in action.

Stack-loading will be really useful for a fixed MG, was thinking of using a preservable magazine item but straight-up stack loading sounds better.
Not sure what to suggest for failed fire skill gain.
Do you know about setting job.expire_timer = 20 and job.flags.store_item = true to make the job expire rather than complete?
Just seemed like something that might be useful to you.

About this...Since modding stone boiling points post-embark works, I wonder whether temporarily tagging the syndromes with that in df.global.world.raws on explosion would work.

Though one may consider it undesirable.

Thanks, I just hope better modders than I continue to run with it. DF needs guns!
Tried a few things regarding venom: flipping syndrome contact bits (did nothing afaict), attempted to insert the needed line into the raws (crashed), couldn't get anything to work. Must have just been inexperience.
In the end I just used the mods settings menu to backup all creature raws and then edit any venoms it finds to work on contact. Not a great solution, but it was all I could do at the time.

Don't suppose you have an example of how you changed boiling points to hand? NP if not.
Your way would be far superior, not sure why one might consider it undesirable given it could presumably be changed back after the bang, you might have to explain your thinking on that one.

[thefriendlyhacker]

Alright, I got something presentable at last for both the ranged weapon script and the artillery script.
...

I had a quick look when it released and was very impressed with all the stuff you added (I'll need to take another look for the pseudo-completion timer stuff which I missed).
Wish I had the intelligence to make (or even use) modtool-style scripts but I find them very confusing to work with.
Not had much time to play with it in game yet though which is a shame, looking forward to seeing the organ gun in action.

Heh, fun fact. I am also in the progress of writing a general purpose set of ranged scripts.  They have a shared back end that controls their ordering and passes tags between them so the individual scripts can communicate to each other.   It is still a WIP, but at the moment I have implemented variable rates of fire for hand-held projectile weapons (and it is done in a way that can mimic magazine fed weapons) and multi-shot projectiles.  All I have to do is write a third script that alters velocity (which should be easy) and I can replace all the glob projectile interaction based weapons in my mod with real bullets.

About this...Since modding stone boiling points post-embark works, I wonder whether temporarily tagging the syndromes with that in df.global.world.raws on explosion would work.

Though one may consider it undesirable.

...
Your way would be far superior, not sure why one might consider it undesirable given it could presumably be changed back after the bang, you might have to explain your thinking on that one.

I can probably answer that one.

Changing it's contact/inhale properties is only safe if Dwarf Fortress handles checks concerning contact/inhaled syndrome bearing mats in a stateless way.  If it does keep any sort of state, you run a serious risk of blundering into the programmer's equivalent of !!fun!!, undefined behavior.

Let me give an illustrative example. Lets say that the game mimics the effects of breathing without having to track it explicitly by keeping an array of counters and IDs for contact/inhale syndrome bearing materials that each creature is has recently been exposed to, and when a counter runs out the code for handling that syndrome is run again if the creature is still being exposed appropriately to that material.  Lets say you change a mat's syn to be inhaled, and expose a creature to it.  That creature now has a counter+ID for your mat.  Between it's initial exposure and the counter running out, you change it back to not inhaled.  When the counter runs out, the code that handles inhaled or contact syndrome bearing mats runs on something that has neither a contact or inhaled syn.  What happens? Well, it could assume anything passed to it is one or the other and check with a simple if (syn.inhaled==1) statement, thus treating your mat as contact and breaking any inhaled poisons you do this trick with some of the time.  It could check both types, return the default value of 0/null/false, which could result in correct behavior if 0/null/false is what the code returns if the syndrome isn't supposed to be applied any more...or it could crash the game on the spot by dereferencing a null pointer if it is always meant to return an object.  And of course the checks for if it is contact/inhaled at all could be within the code that gets executed when the counter runs out, meaning it is completely safe to pass that code whatever the hell you want.  Nobody but Toady knows.

This is why when reasonably possible you should try to change DF's memory such that the variables you are altering describe the in-game behavior you are trying to alter in its entirety.  That way, all you have to do is change the set of variables from one valid in-game state to another, and the game will continue to run with the new valid state.  Changing syndrome properties is not the sort of thing you should do when alternatives are possible, because creatures have a lot of data in them about what syndromes affect them, and you have to understand all of it to ensure that you aren't breaking the game in some weird to diagnose manner by changing the materials to something which conflicts with data that may be held within the data structure of individual creatures (or data held somewhere else, for that matter).

[Fleeting Frames]

If it doesn't work, it doesn't work. Gotta use more complex options (such as tagging people caught in geographical location of the cloud with modtools/add-syndrome; note that DF creatures don't breathe all the time so deadly fog isn't guaranteed to hit the whole squad).

Beyond what thefriendlyhacker said (I find if I change something I shouldn't it almost always crashes, but I haven't written any mods) and more in line with editing the raws before worldgen, there's also that by making the syndromes contact ones changes their behaviour everywhere outside the gunshells (i.e. GCS venom pools become legitimate weapons) and such approach not getting other mods a player might use for venom-loading.

Changing stone boiling points is an old practice - here is a reference. I've seen it in mid-action on some dfma maps.

[zilpin]

Wall destruction is impressive.

I'll be watching this.

[Grimlocke]

I just updated my own mod with some fixes including updated targeting that you might find to be of some use. The old one didn't account for floors existing when shooting up/down, and didn't consider fortifications as something it could shoot through. I also used dfhack.units.getUnitsInBox to get only units in potential range rather than iterating through every single unit on the map and sorted them by distance from the gun before checking other conditions.

Spoiler: Targeting functions, not a drop-in replacement as is but the idea shouldn't be hard to carry over (click to show/hide)

function findTarget(gun, gTable, firer, mode)
   local hitList = {}
   local targetList = {}
   if not gTable.props.range then gTable.props.range = { 0, 100 } end
   local unitList = dfhack.units.getUnitsInBox(
   gTable.targetBox1.x, gTable.targetBox1.y, gTable.targetBox1.z,
   gTable.targetBox2.x, gTable.targetBox2.y, gTable.targetBox2.z)
   for _,unit in ipairs(unitList) do
      local circleDist = math.floor(math.sqrt(((gTable.muzzlePos.x - unit.pos.x)^2) + ((gTable.muzzlePos.y - unit.pos.y)^2) + ((gTable.muzzlePos.z - unit.pos.z)^2)) + 0.5 )
      targetList[#targetList + 1] = { unit = unit, circleDist = circleDist }
   end
   table.sort(targetList, function(a,b) return a.circleDist < b.circleDist end)
   for _,target in ipairs(targetList) do
      if target.circleDist >= gTable.props.range[1] and target.circleDist <= gTable.props.range[2] then
         if updateDirection(gun, target.unit, gTable.props.range, 1) then
            --if isHostile(target.unit, firer) then
               local xyzdelta = { x = target.unit.pos.x - gTable.muzzlePos.x, y = target.unit.pos.y - gTable.muzzlePos.y, z = target.unit.pos.z - gTable.muzzlePos.z }
               local squareDist = math.max(math.abs(xyzdelta.x), math.abs(xyzdelta.y), math.abs(xyzdelta.z))
               xyzdelta = { x = xyzdelta.x / squareDist, y = xyzdelta.y / squareDist, z = xyzdelta.z / squareDist }
               if canPathTo(gTable.muzzlePos, xyzdelta, squareDist) == true then
                  hitList[#hitList + 1] = { originPos = gTable.muzzlePos, targetPos = xyz2pos(target.unit.pos.x, target.unit.pos.y, target.unit.pos.z), xyzdelta = xyzdelta }
                  break
               end
            --end
         end
      elseif target.circleDist > gTable.props.range[2] then break end
   end
   return hitList
end

function isHostile(target, firer)
   if target.civ_id ~= firer.civ_id and
   target ~= firer and
   target.flags1.inactive == false and
   target.flags1.diplomat == false and
   target.flags1.merchant == false and
   target.flags2.visitor == false and
   target.flags2.resident == false then
      return true else return false
   end
end

function canPathTo(originPos, xyzdelta, distance)
   local counter = 1
   local isPassable = true
   local pos, prevPos, open, prevOpen
   local allowedTiles = {}
   allowedTiles[1] = true
   allowedTiles[32] = true
   allowedTiles[490] = true
   if dfhack.maps.getTileType(originPos) == 32 or dfhack.maps.getTileType(originPos) == 1 then prevOpen = true else prevOpen = false end
   while counter <= distance do
      prevPos = pos or originPos
      pos = xyz2pos(math.ceil(originPos.x + xyzdelta.x * counter - 0.5),
      math.ceil(originPos.y + xyzdelta.y * counter - 0.5),
      math.ceil(originPos.z + xyzdelta.z * counter - 0.5))
      if dfhack.maps.getTileBlock(pos) ~= nil then
         if open then prevOpen = open end
         if allowedTiles[dfhack.maps.getTileType(pos)] == true then open = true else open = false end
         if dfhack.maps.getTileBlock(pos).walkable[pos.x%16][pos.y%16] == 0 and open == false then
            isPassable = false
            break
         elseif pos.z < prevPos.z then
            if prevOpen == false and allowedTiles[dfhack.maps.getTileBlock(prevPos).tiletype[pos.x%16][pos.y%16]] == true then
               isPassable = false
               break
            end
         elseif pos.z > prevPos.z then
            if open == false and allowedTiles[dfhack.maps.getTileBlock(pos).tiletype[prevPos.x%16][prevPos.y%16]] == true then
               isPassable = false
               break
            end
         end
      end
      counter = counter + 1
   end
   if isPassable then return true else return false end
end

I set the targeting bounding box in checkDirection to prevent it from having to recalculate that on every shot:
   gunTable[gun.id].muzzlePos = xyz2pos(gun.centerx, gun.centery - 1, gun.z)
   gunTable[gun.id].targetBox1 = xyz2pos(math.ceil(gun.centerx + range[2] * 0.82), gun.centery - 1, gun.z + range[2])
   gunTable[gun.id].targetBox2 = xyz2pos(math.ceil(gun.centerx - range[2] * 0.82), gun.centery - range[2], gun.z - range[2])

Hope some of that is of some use.

[Forwe]

Hey, excuse me for a possibly stupid question, but does this mod work nicely with Adventure Mode? I mean, will Blunderbusses shoot in a cone and Machine Guns have short reload times, etc?

[DWARFFRAWD]

Can you add tilesets that work properly with this mod?

Or, can you teach how to make tileset to support this mod?

[zaporozhets]

Hey, excuse me for a possibly stupid question, but does this mod work nicely with Adventure Mode? I mean, will Blunderbusses shoot in a cone and Machine Guns have short reload times, etc?

No such thing as a stupid question, nothing was made with adventure mode in mind and so there are many oddities, but as best I can tell all the weapons still function properly they just don't look nearly as cool.
For example the lightning gun is one of the most script heavy weapons and whilst it works, you'll only see the lightning briefly if at all due to the differences in timescale between fortress and adventure modes.
I'd only recommend it if you really really want guns, your mileage may vary.

Can you add tilesets that work properly with this mod?

Or, can you teach how to make tileset to support this mod?

Sure, what tileset did you want me to add?

If you want to make a tileset work yourself, you'll want to navigate to "Dwarf Fortress/data/init/overrides.txt" and add:

Spoiler (click to show/hide)

[TILESET:musketmod.png:musketmod.png:musketmod_overrides]

after the other tileset definitions (lines beginning with [TILESET:).

Then you'll want to add:

Spoiler (click to show/hide)

[OVERRIDE:228:I:TRAPCOMP:TRAPCOMP:0:musketmod_overrides:83] - cannonball
[OVERRIDE:228:I:TRAPCOMP:TRAPCOMP:1:musketmod_overrides:100] - HE shell
[OVERRIDE:228:I:TRAPCOMP:TRAPCOMP:2:musketmod_overrides:99] - empty cannister
[OVERRIDE:228:I:TRAPCOMP:TRAPCOMP:3:musketmod_overrides:101] - gas cannister
[OVERRIDE:219:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:32]
[OVERRIDE:223:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:33]
[OVERRIDE:47:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:34]
[OVERRIDE:9:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:48]
[OVERRIDE:255:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:49]
[OVERRIDE:8:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:50]
[OVERRIDE:186:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:64]
[OVERRIDE:210:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:65]
[OVERRIDE:240:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:66]
[OVERRIDE:201:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, top row
[OVERRIDE:186:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:51] -cannon, north facing, top row
[OVERRIDE:187:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, top row
[OVERRIDE:198:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, middle row
[OVERRIDE:208:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:67] -cannon, north facing, middle row
[OVERRIDE:181:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, middle row
[OVERRIDE:200:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, bottom row
[OVERRIDE:205:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, bottom row
[OVERRIDE:188:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, bottom row
[OVERRIDE:201:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, top row
[OVERRIDE:210:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, top row
[OVERRIDE:187:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, top row
[OVERRIDE:186:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, middle row
[OVERRIDE:198:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:35] -cannon, east facing, middle row
[OVERRIDE:205:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:36] -cannon, east facing, middle row
[OVERRIDE:200:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, bottom row
[OVERRIDE:208:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, bottom row
[OVERRIDE:188:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, bottom row
[OVERRIDE:201:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, top row
[OVERRIDE:205:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, top row
[OVERRIDE:187:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, top row
[OVERRIDE:198:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, middle row
[OVERRIDE:210:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:37] -cannon, south facing, middle row
[OVERRIDE:181:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, middle row
[OVERRIDE:200:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, bottom row
[OVERRIDE:186:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:53] -cannon, south facing, bottom row
[OVERRIDE:188:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, bottom row
[OVERRIDE:201:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, top row
[OVERRIDE:210:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, top row
[OVERRIDE:187:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, top row
[OVERRIDE:205:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:68] -cannon, west facing, middle row
[OVERRIDE:181:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:69] -cannon, west facing, middle row
[OVERRIDE:186:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, middle row
[OVERRIDE:200:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, bottom row
[OVERRIDE:208:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, bottom row
[OVERRIDE:188:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, bottom row
[OVERRIDE:8:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:80] -alchemist, top row
[OVERRIDE:246:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:81] -alchemist, top row
[OVERRIDE:14:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:82] -alchemist, top row
[OVERRIDE:153:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:96:16] -alchemist, middle row
[OVERRIDE:35:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:97] -alchemist, middle row
[OVERRIDE:15:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:98] -alchemist, middle row
[OVERRIDE:19:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:112] -alchemist, bottom row
[OVERRIDE:154:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:113:16] -alchemist, bottom row
[OVERRIDE:9:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:114] -alchemist, bottom row
[OVERRIDE:47:I:WEAPON:WEAPON:24:musketmod_overrides:0] - musket
[OVERRIDE:47:I:WEAPON:WEAPON:25:musketmod_overrides:1] - launcher
[OVERRIDE:47:I:WEAPON:WEAPON:26:musketmod_overrides:2] - mortar
[OVERRIDE:47:I:WEAPON:WEAPON:27:musketmod_overrides:3] - pistol
[OVERRIDE:47:I:WEAPON:WEAPON:28:musketmod_overrides:4] - bayonet
[OVERRIDE:47:I:WEAPON:WEAPON:29:musketmod_overrides:5] - bayonetted musket
[OVERRIDE:47:I:WEAPON:WEAPON:30:musketmod_overrides:6] - bayonetted pistol
[OVERRIDE:47:I:WEAPON:WEAPON:31:musketmod_overrides:7] - blunderbuss
[OVERRIDE:47:I:WEAPON:WEAPON:32:musketmod_overrides:8] - dragon pistol
[OVERRIDE:47:I:WEAPON:WEAPON:33:musketmod_overrides:9] - automusket
[OVERRIDE:47:I:WEAPON:WEAPON:34:musketmod_overrides:10] - tesla gun
[OVERRIDE:47:I:AMMO:AMMO:3:musketmod_overrides:16] bullets
[OVERRIDE:47:I:AMMO:AMMO:4:musketmod_overrides:17] rockets
[OVERRIDE:47:I:AMMO:AMMO:5:musketmod_overrides:18] grenades
[OVERRIDE:47:I:AMMO:AMMO:6:musketmod_overrides:23] cartridges
[OVERRIDE:47:I:AMMO:AMMO:7:musketmod_overrides:24] shot
[OVERRIDE:47:I:AMMO:AMMO:8:musketmod_overrides:26] battery

Somewhere with the other overrides (not sure it matters where).

[DWARFFRAWD]

Hey, excuse me for a possibly stupid question, but does this mod work nicely with Adventure Mode? I mean, will Blunderbusses shoot in a cone and Machine Guns have short reload times, etc?

No such thing as a stupid question, nothing was made with adventure mode in mind and so there are many oddities, but as best I can tell all the weapons still function properly they just don't look nearly as cool.
For example the lightning gun is one of the most script heavy weapons and whilst it works, you'll only see the lightning briefly if at all due to the differences in timescale between fortress and adventure modes.
I'd only recommend it if you really really want guns, your mileage may vary.

Can you add tilesets that work properly with this mod?

Or, can you teach how to make tileset to support this mod?

Sure, what tileset did you want me to add?

If you want to make a tileset work yourself, you'll want to navigate to "Dwarf Fortress/data/init/overrides.txt" and add:

Spoiler (click to show/hide)

[TILESET:musketmod.png:musketmod.png:musketmod_overrides]

after the other tileset definitions (lines beginning with [TILESET:).

Then you'll want to add:

Spoiler (click to show/hide)

[OVERRIDE:228:I:TRAPCOMP:TRAPCOMP:0:musketmod_overrides:83] - cannonball
[OVERRIDE:228:I:TRAPCOMP:TRAPCOMP:1:musketmod_overrides:100] - HE shell
[OVERRIDE:228:I:TRAPCOMP:TRAPCOMP:2:musketmod_overrides:99] - empty cannister
[OVERRIDE:228:I:TRAPCOMP:TRAPCOMP:3:musketmod_overrides:101] - gas cannister
[OVERRIDE:219:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:32]
[OVERRIDE:223:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:33]
[OVERRIDE:47:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:34]
[OVERRIDE:9:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:48]
[OVERRIDE:255:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:49]
[OVERRIDE:8:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:50]
[OVERRIDE:186:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:64]
[OVERRIDE:210:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:65]
[OVERRIDE:240:B:WORKSHOP_CUSTOM:Workshop:GUNSMITH:musketmod_overrides:66]
[OVERRIDE:201:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, top row
[OVERRIDE:186:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:51] -cannon, north facing, top row
[OVERRIDE:187:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, top row
[OVERRIDE:198:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, middle row
[OVERRIDE:208:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:67] -cannon, north facing, middle row
[OVERRIDE:181:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, middle row
[OVERRIDE:200:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, bottom row
[OVERRIDE:205:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, bottom row
[OVERRIDE:188:B:WORKSHOP_CUSTOM:Workshop:CANNON_N:musketmod_overrides:52] -cannon, north facing, bottom row
[OVERRIDE:201:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, top row
[OVERRIDE:210:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, top row
[OVERRIDE:187:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, top row
[OVERRIDE:186:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, middle row
[OVERRIDE:198:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:35] -cannon, east facing, middle row
[OVERRIDE:205:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:36] -cannon, east facing, middle row
[OVERRIDE:200:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, bottom row
[OVERRIDE:208:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, bottom row
[OVERRIDE:188:B:WORKSHOP_CUSTOM:Workshop:CANNON_E:musketmod_overrides:52] -cannon, east facing, bottom row
[OVERRIDE:201:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, top row
[OVERRIDE:205:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, top row
[OVERRIDE:187:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, top row
[OVERRIDE:198:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, middle row
[OVERRIDE:210:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:37] -cannon, south facing, middle row
[OVERRIDE:181:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, middle row
[OVERRIDE:200:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, bottom row
[OVERRIDE:186:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:53] -cannon, south facing, bottom row
[OVERRIDE:188:B:WORKSHOP_CUSTOM:Workshop:CANNON_S:musketmod_overrides:52] -cannon, south facing, bottom row
[OVERRIDE:201:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, top row
[OVERRIDE:210:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, top row
[OVERRIDE:187:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, top row
[OVERRIDE:205:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:68] -cannon, west facing, middle row
[OVERRIDE:181:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:69] -cannon, west facing, middle row
[OVERRIDE:186:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, middle row
[OVERRIDE:200:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, bottom row
[OVERRIDE:208:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, bottom row
[OVERRIDE:188:B:WORKSHOP_CUSTOM:Workshop:CANNON_W:musketmod_overrides:52] -cannon, west facing, bottom row
[OVERRIDE:8:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:80] -alchemist, top row
[OVERRIDE:246:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:81] -alchemist, top row
[OVERRIDE:14:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:82] -alchemist, top row
[OVERRIDE:153:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:96:16] -alchemist, middle row
[OVERRIDE:35:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:97] -alchemist, middle row
[OVERRIDE:15:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:98] -alchemist, middle row
[OVERRIDE:19:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:112] -alchemist, bottom row
[OVERRIDE:154:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:113:16] -alchemist, bottom row
[OVERRIDE:9:B:WORKSHOP_CUSTOM:Workshop:ALCHEMIST:musketmod_overrides:114] -alchemist, bottom row
[OVERRIDE:47:I:WEAPON:WEAPON:24:musketmod_overrides:0] - musket
[OVERRIDE:47:I:WEAPON:WEAPON:25:musketmod_overrides:1] - launcher
[OVERRIDE:47:I:WEAPON:WEAPON:26:musketmod_overrides:2] - mortar
[OVERRIDE:47:I:WEAPON:WEAPON:27:musketmod_overrides:3] - pistol
[OVERRIDE:47:I:WEAPON:WEAPON:28:musketmod_overrides:4] - bayonet
[OVERRIDE:47:I:WEAPON:WEAPON:29:musketmod_overrides:5] - bayonetted musket
[OVERRIDE:47:I:WEAPON:WEAPON:30:musketmod_overrides:6] - bayonetted pistol
[OVERRIDE:47:I:WEAPON:WEAPON:31:musketmod_overrides:7] - blunderbuss
[OVERRIDE:47:I:WEAPON:WEAPON:32:musketmod_overrides:8] - dragon pistol
[OVERRIDE:47:I:WEAPON:WEAPON:33:musketmod_overrides:9] - automusket
[OVERRIDE:47:I:WEAPON:WEAPON:34:musketmod_overrides:10] - tesla gun
[OVERRIDE:47:I:AMMO:AMMO:3:musketmod_overrides:16] bullets
[OVERRIDE:47:I:AMMO:AMMO:4:musketmod_overrides:17] rockets
[OVERRIDE:47:I:AMMO:AMMO:5:musketmod_overrides:18] grenades
[OVERRIDE:47:I:AMMO:AMMO:6:musketmod_overrides:23] cartridges
[OVERRIDE:47:I:AMMO:AMMO:7:musketmod_overrides:24] shot
[OVERRIDE:47:I:AMMO:AMMO:8:musketmod_overrides:26] battery

Somewhere with the other overrides (not sure it matters where).

Oh, thanks for kind instruction.
Sorry for my insufficient explanation.
 
But i mean,
In readme file, it said this mod works only in ascii or meph graphic set.

Can i make it change to works with other graphic set?

I had played in ascii version but now i want to change graphic to spacefox.

[zaporozhets]

Oh, thanks for kind instruction.
Sorry for my insufficient explanation.
 
But i mean,
In readme file, it said this mod works only in ascii or meph graphic set.

Can i make it change to works with other graphic set?

I had played in ascii version but now i want to change graphic to spacefox.

The problem is that the tileset included with the mod is at 32x32 resolution, whereas spacefox is 16x16.
You could try simply halving the resolution, but I had a quick go in GIMP and it looks pretty bad without retouching everything.
Ideally new graphics would need to be drawn for everything at that resolution, but I'm no artist and I'm finding free time a little hard to come by ATM to even make something as paltry as my ability would allow.
Sorry I can't be more help, I do want to add compatibility for smaller tilesets at some point.