Print

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

[Raidau]

PTW, great work, also letting you know that 3.2 is in latest Macnewbie.

However: I copied the item_description folder to df/raw and to save/raw, but can't make descriptions appear in game.

Spoiler (click to show/hide)

According to debug mode this is the path the script tries to access:

Code: [Select]

/Applications/Macnewbie_9.16/Macnewbie/Dwarf Fortress/data/save/region3-lowfps\raw\item_descriptions\WEAPON\ITEM_WEAPON_AXE_BATTLE.txtNote the difference in slashes after data/save/ I suspect this issue is present on linux too.

A different issue is with material properties illustrated here:

Spoiler (click to show/hide)

Those long lines need to be formatted differently to be usable.

1. Replaced the slashes in new version (which has been released just now)

2. I tested this with twbt and its standatd text tileset. I was to lazy to switch to 2D and check how it looks Ok its now just "fr." and" el.", hope this will be enough for strings to fit the screen.

I think we could really need some repository with descriptions. Its quite a tedious and long work, yet all it needs is to make summaries of wiki articles Just need to decide which forum section that thread will suit

[lethosor]

Have you considered hosting this on Github (or another git host)? It would make tracking and merging changes a lot easier, if it were to be included in DFHack, compared to downloading a single compressed file and trying to merge changes by hand. Scripts included in DFHack that are solely hosted on DFFD tend to become outdated quickly (see dfstatus for an example).
Also, this really should be in the utilities subforum.

[Sergarr]

:O

this is so awesome

[fricy]

1. Replaced the slashes in new version (which has been released just now)
2. I tested this with twbt and its standatd text tileset. I was to lazy to switch to 2D and check how it looks Ok its now just "fr." and" el.", hope this will be enough for strings to fit the screen.

Descriptions work now, and I think with fr. and el. the screen is usable.
There's a small problem with the line endings, the windows EOL symbols are interpreted as music notes on mac, converting to unix line endings solved this on my end.

ASCII pictures are still not displayed. Is there some configuration I'm missing to make them work?

Have you considered hosting this on Github (or another git host)? It would make tracking and merging changes a lot easier...
Also, this really should be in the utilities subforum.

Strongly agreed.
@lethosor: Since the wiki already stores all the raws and the descriptions, do you think there's an easy way to generate a bunch of text files from that db with the descriptions and the proper file names to kickstart this project?

[lethosor]

@lethosor: Since the wiki already stores all the raws and the descriptions, do you think there's an easy way to generate a bunch of text files from that db with the descriptions and the proper file names to kickstart this project?

There's no difference between what's stored on the wiki and the raw files (in fact, the raws on the wiki may be outdated).

[Dirst]

@lethosor: Since the wiki already stores all the raws and the descriptions, do you think there's an easy way to generate a bunch of text files from that db with the descriptions and the proper file names to kickstart this project?

There's no difference between what's stored on the wiki and the raw files (in fact, the raws on the wiki may be outdated).

For items that have descriptions in the raws, the wiki shows them in italics at the beginning of the article.  fricy is asking for the equivalent text being extracted from the wikitext so that it can be made into a brief description for a vanilla item that doesn't have a DESCRIPTION tag.

Gems seem to do this fairly consistently; I'm not sure what else on the wiki is that predictable.

[lethosor]

@lethosor: Since the wiki already stores all the raws and the descriptions, do you think there's an easy way to generate a bunch of text files from that db with the descriptions and the proper file names to kickstart this project?

There's no difference between what's stored on the wiki and the raw files (in fact, the raws on the wiki may be outdated).

For items that have descriptions in the raws, the wiki shows them in italics at the beginning of the article.  fricy is asking for the equivalent text being extracted from the wikitext so that it can be made into a brief description for a vanilla item that doesn't have a DESCRIPTION tag.

Gems seem to do this fairly consistently; I'm not sure what else on the wiki is that predictable.

It would be easier to extract that text from the raws - it's only the value of the [DESCRIPTION] token for creatures. (What items are you referring to?)

[Dirst]

@lethosor: Since the wiki already stores all the raws and the descriptions, do you think there's an easy way to generate a bunch of text files from that db with the descriptions and the proper file names to kickstart this project?

There's no difference between what's stored on the wiki and the raw files (in fact, the raws on the wiki may be outdated).

For items that have descriptions in the raws, the wiki shows them in italics at the beginning of the article.  fricy is asking for the equivalent text being extracted from the wikitext so that it can be made into a brief description for a vanilla item that doesn't have a DESCRIPTION tag.

Gems seem to do this fairly consistently; I'm not sure what else on the wiki is that predictable.

It would be easier to extract that text from the raws - it's only the value of the [DESCRIPTION] token for creatures. (What items are you referring to?)

Pretty much every item in the game that can be "viewed" but doesn't have a description in the raws (weapons, armor, tools, toys, etc.) plus all of the materials.  As I said, the gems might work, but I'm not too hopeful of finding a useable pattern in items' wikipages.

[Raidau]

ASCII pictures are still not displayed. Is there some configuration I'm missing to make them work?

"ascii_item" and "ascii_unit" arguments enable corresponding ascii art

UPDATE: Added the script and the repository to GitHub

[Putnam]

Fracture/Yield are in Kilopascals, btw.

[Raidau]

Fracture/Yield are in Kilopascals, btw.

thx, but I think i better omit the units to make lines shorter

[Putnam]

Wait, or maybe just pascals. Either way, it's 2-3 character (kPa, Pa)

[Meph]

I agree, this should be in utilities.

Once a complete set with descriptions and ascii art is done, it can be released as a mod.

[Sergarr]

Yields for steel should be in the ballpark of 200 MPa so tread accordingly

[Warmist]

Oh man i was hoping that somebody does this! First time my laziness pays off