Print

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

[pisskop]

oh my

[Warmist]

Hmm now that i look at this, you are using default viewscreen and just adding new strings to it. Maybe it would be better to have a new screen alltogether (and then e.g. canceling would quit from both screens). Though you would need to re-implement old behavior (reaction products?) but you could have more features (e.g. hyperlinks for item material/syndromes/castes/whatever, inline ascii art).

If you would like that i could try to make tutorial-ish viewscreen example.

[Raidau]

Hmm now that i look at this, you are using default viewscreen and just adding new strings to it. Maybe it would be better to have a new screen alltogether (and then e.g. canceling would quit from both screens). Though you would need to re-implement old behavior (reaction products?) but you could have more features (e.g. hyperlinks for item material/syndromes/castes/whatever, inline ascii art).

If you would like that i could try to make tutorial-ish viewscreen example.

Well, dfhack screens are a big mystery for me. Are you talking about a full reimplementation of item view screen built inside a single DFHack screen? Hyperlinks and all that kind of stuff would be incredible, but that will take a lot of time (I am trying to finish my Natural Balance alpha and upload it ASAP).

There is an upside of using existing DF screen - it supports truetype.

All the modders (I suppose) would appreciate such tutorial

[PeridexisErrant]

My vote is to go for it - this would be amazing, and Truetype is no loss anyway, since it's buggy and utterly inferior to TwbT. Whoever want to do it, go crazy!

[Meph]

Both the Starter pack and Masterwork use Twbt by default, which excludes truetype. I assume that most people play without ttf by now. Most people that use fancy utilities and mods, that is.

[scamtank]

Yo I caught a dumbass little bug in how soap materials are reported.



How silly it looks! Turns out, this:

Code: [Select]

table.insert(list,"Used to make soap"..dfhack.matinfo.decode(mat_type, mat_index).material.state_name.Liquid)
...should rather read like this:

Code: [Select]

table.insert(list,"Used to make "..dfhack.matinfo.decode(mat_type, mat_index).material.state_name.Solid)


All better now! I'm guessing there's still some snags left, I'll report any I find.

[Raidau]

Yo I caught a dumbass little bug in how soap materials are reported.

Looks like i was hasty adding those usage lines when decided to make it show actual result instead of just plain "used to make soap". Fixed that

[Meph]

So... oil has a sharpness? Ok.

Edit: (to say something constructive at least): Do you think it makes sense to post so many numbers? People that know what the molar mass, shear yield, impact yield, etc, mean are usually the same that can read raws.

But this should be a help for players, easy to understand. Maybe it could be more user-friendly, using descriptions/adjectives instead of numbers?

[Putnam]

So... oil has a sharpness? Ok.

Edit: (to say something constructive at least): Do you think it makes sense to post so many numbers? People that know what the molar mass, shear yield, impact yield, etc, mean are usually the same that can read raws.

But this should be a help for players, easy to understand. Maybe it could be more user-friendly, using descriptions/adjectives instead of numbers?

All items have sharpness.

Molar mass isn't really important, but yields/fractures are all very important to understand how the material works relative to other materials, and in very specific circumstances. For example, BENDING afaik is only used with joint locks and TORSION with non-edged latches (of which there are 0 in vanilla DF)

[scamtank]

Ooh hey I have a suggestion now.

Replace this:

Code: [Select]

table.insert(list,"Temperature: "..item.temperature.whole.."U")
...with this:

Code: [Select]

table.insert(list,"Temperature: "..item.temperature.whole.."U ("..math.floor((item.temperature.whole-10032)/1.8).." C)")
...for a temperature reading that humans can understand instantly.



(I can't make the °-sign appear right )

[Warmist]

I made a tutorial (at least a start of it) here: thread about gui making.

[Raidau]

Ooh hey I have a suggestion now.

Replace this:

Code: [Select]

table.insert(list,"Temperature: "..item.temperature.whole.."U")
...with this:

Code: [Select]

table.insert(list,"Temperature: "..item.temperature.whole.."U ("..math.floor((item.temperature.whole-10032)/1.8).." C)")
(I can't make the °-sign appear right )

Well, right, I was thinking on that but somehow decided to just pass it by. The temperature grade in DF is strange in many places... Its just not like real-world temperature, U suits better XD. Gonna add this by your request.

The material data is currently shown for every item, but sometimes it does not make sence, I agree. Thats just one of the things I ignored for the start The ignored item type list can be done with ease

[Raidau]

So... oil has a sharpness? Ok.

Edit: (to say something constructive at least): Do you think it makes sense to post so many numbers? People that know what the molar mass, shear yield, impact yield, etc, mean are usually the same that can read raws.

But this should be a help for players, easy to understand. Maybe it could be more user-friendly, using descriptions/adjectives instead of numbers?

If someone provides me enough adjectives to express all the complexity of DF material properties, I will include this But I think the numbers and comarison percentages are good for the time being

UPDATE: updated the script 

[Max™]

Seeing this it feels like it should be like, a default part of the game as is, having the info down there for the material properties is too cool, art and such is a neat bonus, but yeah, despite knowing all the various stats mostly by memory (too many years of gming pen and paper games, I memorize useless stats reflexively) it's still very cool having it presented like that. awesome stuff!

[Raidau]

I think thanks to Warmist now its possible. Behold!

Just recenly recognized that lua can convert character index into the character itself, and custom workshop editor creates the character based images! So I can use it as a simple DF ASCII image editor XD. It allows you to draw picture for any tileset and see how it will look.

Colors are on their way! (I hope, gonna check what I know about pens)