If I get a chance. Been gone a few weeks and found that FGU changes have once again trashed a number of my extensions. Will have to look into those first.Quote:
Originally Posted by spencerg
If I get a chance. Been gone a few weeks and found that FGU changes have once again trashed a number of my extensions. Will have to look into those first.Quote:
Originally Posted by spencerg
I feel your pain.. I just finished a release cycle, 3rd party API annihilated our solution with an update. Fun times. Great work, I always wanted the generic options to be at least visible, people tend to forget they can do more than attack. Out of curiosity, which extensions are you referring too, I believe I have a few of yours!
Here is my current internal list...Quote:
Originally Posted by spencerg
[Keep in mind I have not tried testing everything yet so who knows if it will grow or not. Some of these are purely for myself - as I tend to do things for me and my players - you guys get them as a by product of Grim Press selling them.]
Combat Groups = CT order no longer works in latest FGU update as they now support this - remove all that code and option - work around to get FGU new order stuff to work is to turn off my option.
Assistant GM = on client side can no longer display CT info as it will get both an index field "traits" is nil error and warnings about could not find templates for label_ct_actions and list_ct_actions in client_ct entry.
? = Client double click on map not bringing up the NPC it owns when its not a friendly faction (think it used to or I would have noticed as we have players run other factions all the time) - not sure where this is failing or which extension or FGU raw performs this. Need to get it back to respecting ownership regardless of faction.
Carrier = extension.xml needs new icon name put in for Sir Mott's theme.
Carrier = has weird rotation results when all are drivers and some are carriers for other things - probably just the way it is (rules applied correctly to give garbage - you get what you define) - but make sure.
Death Indicators = can leave tombstone as icon in some cases - need to duplicate and see how this is happening.
Equipped Effects = needs to be tested for performance and streamlining.
Generic actions = has been requested to have optional open/close window option and to have all buttons same size.
New Races in Rime of the Frost Maiden need to be added to a new module for my players as we are starting that campaign - so it points to all spells/feats/etc. from Aridhro supplemental stuff like my AE5ePHBClasses module I gave them.
Attachment 54307 Here's what I made for myself a while ago (ignore the prone thing, I was working on an idea but ran out of time). I can send that to you if you want to just copy itQuote:
Originally Posted by SilentRuin
just hacked this yesterday to same effect, beauty, i got lazy on the offsets. trying to set up syrinscape for first time.Quote:
Originally Posted by ScriedRaven
Well I have a few of those. They’re great. Id write a few myself but i get enough code dumped on me daily that id rather just play. However, i did peek at writing extensions the other day, haven’t seen LUA scripts in along time :)) , blast from past. I love equip effects, bravo on that one
Working on other stuff right now. After its all done I'll see if this is something I want to supply and will look into it. Not sure yet what I want to do as I've not really looked into having it as its own closable window (as the whole purpose was for it always to be in your face so you remember they exist).Quote:
Originally Posted by ScriedRaven
V1.24 - Bug - had to fix onInit() checks - if a option has never been toggled it will not be in db.xml and the check will fail to find it - even though has been registered.
Technical developer info:
If you do operation in onInit (now onDesktopInit as of the fix I'm doing) then you can't use OptionsManager.isOption check as the client will only ever get the default value. So I had to switch to checking via CampaignRegistry - but now it turns out if you've never actually set the option (or toggled it) it will not be in <options> of db.xml and will not be defined in the CampaignRegistry. So to fix all this I've had to move my onInit() checks that do ActionsManager.registerResultHandler into onDesktopInit and also insure immediately after I call OptionsManager.registerOption2 I have to do something like OptionsManager.setOption("VERIFY_ATTACK_TYPE", OptionsManager.getOption("VERIFY_ATTACK_TYPE")); to insure that its in the local CampaignRegistry. Technically I would only have to do that once ever in a campaing to get it in db.xml but for saftey's sake I just always do it after I OptionsManager.registerOption2 the option. Crazy stuff. But nobody really cares as long as the fix works, noting in case I need to remember why I did all that.
Thanks SR for keeping these so updated and always trying to fix them to work the best they can.
Will probably simplify that coding next time I'm in based on talk with Moon Wizard and onDesktopInit() supposedly supporting the client side using isOption at that point - for now I'm leaving it till next time I'm forced to fix something.