1. Could be a good way to make it work, but I'd like to see the tree as is with thinner boxes to compare the current, planned hover update, and an as is but less wide version.
2. All of this sounds cool
3. Not sure what you need feed back for.
Printable View
1. Could be a good way to make it work, but I'd like to see the tree as is with thinner boxes to compare the current, planned hover update, and an as is but less wide version.
2. All of this sounds cool
3. Not sure what you need feed back for.
1) Personally I am not a fan of hovering over them to see them. As long as it fits the descriptions in the boxes I don't have a problem. Is the scroll wheel not do able? If people think the overall box is too big It might be an issue with screen real-estate. They should be able to use the scale ui command or minimize it when not needed.
2 and 3) Sounds good to me.
I reuploaded the Libraries to reflect the changes made by Johniba.
Also I noticed I haven't looked at the Genesys Libraries lately and there are a few things I need to do to bring them up to date with the changes that have been made to the ruleset since then.
Heck, I still think they're a bit too small! The boxes are still a bit too small when using larger fonts. The standard text on FGU is uncomfortably small.
Just having the name of the talent and its xp cost in the box would be fine, though, if you could click on the box to bring up a description. Likely no need for a mouseover popup.
A thought on organization: moving Descriptions backup into the Library Tab instead of the Campaign Tab, as campaign is already pretty full.
After Sevrick's update, everything looks great on the Vehicles front. So much nicer to be able to search by type now!
An idea for consolidation: perhaps have 3 tabs at the top of the notes section on NPCs, and skill descriptions, Age of Rebellion, Edge of the Empire, and Force and Destiny. That way the player and or DM could have the descriptions of all three in once place. I think the Talents are all identical so nothing is necessary in that vein for that area.
Thanks again Johniba and Sevrick for all you do on this project!
There is one big issue with that
From the beginning, Sevrick has been working on each of the three pillars of the Star Wars RPG as a separate module.
So if a record exist in each, like for example a skill or an npc... they each ARE a individual record
FG does not have advanced database relationships, there is no way to consolidate the record apart form actually having only one module, and rework each record, deleting duplicates, maybe reworking the Source field to allow more than one source, etca
I know there are going to be a few exceptions: I dont remember now, but I have seen a few records for either npc, vehicle or something that in one book has a small stat difference from another book.
It all depends on what you all think, and in the end, what sevrick wants to do with his libraries.
The number of entries that would require all three or even more than just one is pretty small. If the box was there, it wouldn't be difficult to cut out some of the repeats with a simple copy from one and paste onto the other. As always i speak from complete ignorance of what it would take to code that but stylistically regarding consolidation, it would be very nice. Bottom of the pile though, and I'd like to see a planetary tab long before it makes sense to work on what we're talking about here.
I knew there would always be some duplicates just like the official Rules. Multiple Core Rulebooks does that. Even the compendiums will have the most duplicates undoubtably.
There are some things that are weird by creating additional libraries too. I noticed while working on the Clone wars Era Library that I will have to re add the skills. The thing is which descriptions do I use for it? Since there are no descriptions for the skills in those books.
When I finally complete the libraries, I thought about adding 1 library with everything. The thing is this would entail me making a new Campaign and opening up all my libraries a dragging them one by one into the new library. Dont get me wrong I up to the task but is low on the priority list right now.
Not to mention that I would have to maintain another instant of everything. I would start to wonder if I made changes in one library that I didnt in the other.
One last thing load times might be a factor. I am not sure how it will effect performance having every record in one library. Having every record would create massive lists you have to sift through. I suppose as we get better filters this wont be too much of an issue.