Print

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

[Meph]

Yeah, I got really carried away with the new features, but most of them are a basic version of what I planned to do. I just wanted to see the feedback, if people like or dislike them. I sadly dont get enough of this... like: Arbalest is nice, but hard to micromanage, I like how difficult it is to build, Its too hard to make, its too powerful or not. Things like that. I dont play much, especially on a netbook while on the road, so actual fortress reports would be fine.

[Felius]

I'll get back to you on that after I actually manage to get a better handle on the military to start with.

Speaking of military, a brief issue: Uniform Material: Sometimes it gets annoying to pick one in the military screen because there's a bunch of duplicates, even disregarding the overly long list. Chitin and Scaleplate comes to mind. Picking the wrong duplicate can leave your soldier without equipment, and if you are layering stuff, it can be really annoying to fix.

[Meph]

I am aware of that, but dont know how to affect that in any sensible degree... I can only advice to use "specific items", which is what I do.

[Asva]

Meph,
I'm currently working on raw extraction sctipt (forked from Quetust project) aimed to simplify MDF wiki editing.
At the moment it does:

• Numbered list of reactions for workshop.
• Table reaction|description.
• Check if reaction number N is last in the list.
• Keybind for workshop or reaction.
• Reaction of profession, workshop of profession lists and such.
• Colourful ASCII image of workshop.

Raws should be stored on the server (could be done rather quickly).
In the future it's kinda possible:

• Add tileset support (by means of lethosor's java magic).
• Get components of reactions (with tiles and quantities).
• Add various checks to simplify your debug. Which I'm going to discuss in more detail.

For debug purposes I can check for duplicates (of any kind), tags inside the object, extract [DESCRIPTION:blabla] tag from raws etc. Which can be condensed in one big table.
In case you think something could be added | is useless | requires consideration - ask right away. 

[Billy Jack]

@Asva

That sounds great. Just one request.
    After looking at the RAW you have on github, be sure to go through and remove any of the optional entries such as those beginning with !NOPET!.  It would be nice if whatever is added to the MW Wiki, includes all optional items as well.

[Asva]

Billy Jack,
Useful notice. I can get rid of these on the fly. Though, orc fortress uses "YESORC". So it would be "YESORC"->"" and "!ANYWORD!" -> "[", it seems.

It would be nice if whatever is added to the MW Wiki, includes all optional items as well.

Don't quite understand, what those "optional items" are.
Edit: nevermind, figured that.

[vonsch]

Just noticed:

In the current manual under Temple of Armok:

Praying for a golem heart has a small chance of getting the heart, or even turning your worker into a golem directly. It needs iridium, which is very rare. Each ore in the game carries 1% base orichalcum, so you need to do a lot of smelting.

[Meph]

Meph,
I'm currently working on raw extraction sctipt (forked from Quetust project) aimed to simplify MDF wiki editing.
At the moment it does:

• Numbered list of reactions for workshop.
• Table reaction|description.
• Check if reaction number N is last in the list.
• Keybind for workshop or reaction.
• Reaction of profession, workshop of profession lists and such.
• Colourful ASCII image of workshop.

Raws should be stored on the server (could be done rather quickly).
In the future it's kinda possible:

• Add tileset support (by means of lethosor's java magic).
• Get components of reactions (with tiles and quantities).
• Add various checks to simplify your debug. Which I'm going to discuss in more detail.

For debug purposes I can check for duplicates (of any kind), tags inside the object, extract [DESCRIPTION:blabla] tag from raws etc. Which can be condensed in one big table.
In case you think something could be added | is useless | requires consideration - ask right away. 

This sounds like a very powerful tool, especially for the wiki. Be sure to check out the next manual, because I used Roses Python script to separate the reaction raws into single building files.

I wouldnt start on any of the metatags, the YESORC and !NOSSC! yet, because they havent been updated in 4 months, and I will start working on them in 2 weeks, when I am back in Germany. This means you would do work that will be undone, so better wait till I have updated them.

[Tierre]

I coulfn't find the picture with dwarves caste description in the manual folder. So the link in the manual for castes is not working as it can't find the picture. Also..... finding that little link about castes took a lot of time, then i started searching for it to check something. Not the most obvious location:(

[silentdeth]

Probably because caste were replaced with guilds several versions ago.

[Tierre]

Well yeah, but there's still a link to that caste picture in settings part of the manual:)

[Felius]

The Weapon page needs to be updated. It still lists all kinds of bows as trade only, while the workshop page lists them as being built in the fletcher workshop. There might be other issues, but those are the ones I found so far.

[oneuristtwourists]

it's fairly minor, but the tailor entry links to reaction_brewery.txt instead of reaction_tailor.txt.


Also, the clothing sets still state that they need 5 units to create 2 shoes, 2 gloves, 1 shirt and 1 trouser, but you actually only need 3 and create 1 shirt, 1 pants and 2 shoes.


That being said, really loving the extra information.

I can understand that you might want to keep the tables slightly out of the way of newer players, but wouldn't it be better to have them in their own pages?

 As it is, in order to reach the tables for, say, weapons, you have to first go to introduction, then the weapons link there, instead of simply going to the "weapons and armo(u)r" section.

Just a suggestion.


edit: i actually went and checked all the workshops, and found the same issue with screw press, fletcher, furniture, painter, stonecutter, greater dyery and pottery.

[lethosor]

I wouldnt start on any of the metatags, the YESORC and !NOSSC! yet, because they havent been updated in 4 months, and I will start working on them in 2 weeks, when I am back in Germany. This means you would do work that will be undone, so better wait till I have updated them.

Are you changing the syntax of the metatags, or just the names? If you're only changing the names, it wouldn't make a difference - I could still enable/disable all of them using a regex, regardless of their names (for wiki use, that is, since that wouldn't be very useful in an actual MDF game).

[Meph]

If by names you mean the button names, then yes/no/maybe. The syntax as well. Most old tags will stay just like they are, but many will be deleted or moved, and many new ones will be added. Remember, the mod had 5 updates without a change on the GUI. its really very outdated.