All Projects


IDSeverity[[state]]OpenedOpened byAssigned ToSummary[[changedby]]Last EditedPrivate
2532Low29.11.2008ORead, unread, and updated books26.12.2009No2 Task Description

I don’t spend my life in Jayose’s library. However, once in a while, I would go there and spend a couple of hours reading, looking for new books, sometimes refreshing my memory with older ones.

It would be nice if there was a way to quickly spot a book that one has already read. Maybe a (read) or (unread) mark after the title, or just a different colour for the title font, anything as see fit. A “read” flag would be set as soon as the book is open, to keep it simple, and of course it is the player’s responsibility to read the content. Ok, so far, you can tell me that it’s up to me to remember if I read something or not; even when hundreds of volumes will be available; yes, but…

It gets useful when a book is updated. If I do remember that I read a specific book, well, I’ll probably won’t read it again. Meanwhile, words may have been changed inside, following the inconsistencies hunt, world development, whatever… So, if all statuses are set back to “unread” for all players after a change (or from “read” to “updated” if you want to be more precise), we’ll know that we’d better read it again.

It can be a bit heavy on the database (flagging each book for each player), but at least it’s technically simple. Not to mention other uses you could come up with (quest requisites, statistics for the setting team, etc.)

Also, as Tontow suggested, the info can be stored on the client side instead of a database. To not lose the functionality of the “updated” flag, which is set on the server side, a last updated timestamp for each book is all that is needed on the server. Client side, the log starts empty (no book read). When opening a book, the log is updated (each time) with the book id (its name, I suppose) and the opening timestamp (server time, easier than GMT). When examining a shelf, books are marked according to the log info; thus, if the latest opening date is earlier than the book’s server timestamp, it appears as “updated”.

(Wish list reference: http://hydlaa.com/smf/index.php?topic=34222.0)

881Low01.01.2008OFrank BartonRizinAngelaDavide VescoviniAnimal parts economy14.11.2023No9 Task Description

I would suggest a specific hunting skill to “loot” animals instead of the current lottery system giving hides, claws, eyes, and whatnot.

Currently, anybody who can kill something can get enough parts by slaughtering a big amount of creatures. The skill would clearly separate the warriors from the hunters. Anyone can probably cut a rat’s tail, but skinning the animal is a bit more complex. And so on, some beasts will be more difficult to skin than others. Even proper meat is not obvious to extract from a carcass.

As a side effetc, maybe a killer could carry back the entire beast to a person capable of skinning/cutting it, if he doesn’t have the skill himself (it looks like some people can carry 400 kgs out there).

This incidentally could create a real market between players, akin to the economy currently existing around ore and weapons. Obviously, some PCs are going to be cooks, leatherworkers or alchemists.

This of course doesn’t apply to looting rogues, unless one can think of using human parts in some dark alchemy, or just carrying ears or heads as trophies.

Showing tasks 1 - 2 of 2 Page 1 of 1

Available keyboard shortcuts

Tasklist

Task Details

Task Editing