Graphic assets - Best Practices?

[Varsuuk]

For now, when I grab an asset from another non-derived-from (CoreRPG in this case) ruleset, I copy the frame/icon/etc to my own ruleset directory and in hr xml I put a comment on where it came from. I write comment saying from 5E, 2E, or CnC so I know to review at end when work on the “look/theme”(which ai suck at lol) especially when using graphics from things like Castles & Crusades which is not likely cool to use. But this helps me “big picture” before I customize.

Assuming I can legally use a graphic, like from CoreRPG - what makes most sense? Right now, I just reference it vs include a se one copy to “freeze” it. For sideways and temp “borrows” I copy them since I know I won’t be referencing them in final builds.

Referencing CoreRPG makes sense but it later occurred to me, I’m not taking ALL from Core so if for some reason CoreRPG is tweaked in look, it will likely no longer “mesh” with the rest of my theme (...) But is this something to take into consideration? Or we can feel certain that future changes to CoreRPG look if SW decided to do so, would be in extensions vs changing resources so many derived rulesets use.

For now continuing to reference...

[Moon Wizard]

Whether you can use a graphic asset is a licensing question to whomever created the asset. For content included in our rulesets, we typically allow people to use as long as the material is made freely available to the community or sold on the FG store.

For referencing CoreRPG, we will be changing the way that the graphics are used over time, in order to keep the core ruleset code moving forward. There's already a new sidebar button in FGU that will impact many rulesets, as well as the fact that we may change the way the sidebar works long term to make adding record types easier. Also, we know that the radial menu graphics will be changing as well long term to take advantage of changes made for FGU/FGC clients to make theming easier. So, there's no assumption that can be made on this part, but we do plan to communicate via beta testing announcements to make community developers aware of changes that could affect them.

Regards,
JPG

[Varsuuk]

Thanks Moon.

I was backtracking a decision I made and taking advantage of that to document some of the sources to make later replacement (due to licensing or choice) easier.

Since static pngs in CoreRPG is not certain, I’ll take this time to create a graphics/frame/CoreRPG to store the ones I use (and other equiv dirs) so I can avoid documenting everything now that I won’t be straight referencing.

Thanks for the info