I would think general suggestions would be possible, but don't know if they would ever be used.
Something like:
decals and background should be in the 10-25 loadorder
chat related in the 25-50 range
new functionality in the 50-75
rulesets in the 75-100
But I don't know if any of that makes sense or would even in reality be helpful. Just an idea trying to help with the OP.
Actually, probably the reverse order. Functionality should load first (i.e. lower numbers), and modifications and theming should load last (i.e. higher numbers).
Rulesets will always load first, and the layers will load in the order defined by the selected ruleset for the campaign.
Cheers,
JPG
Thank you everyone for your input. The above discussion begs the possibility of two documents, a best practices for extension developers and a troubleshooting guide for extension users (and developers to give to their users).
Below is a first cut for the troubleshooting guide. I would like for it to be a "living document", we've put in a bit of work here and it would be great if that work didn't have to be repeated. Should you decide to review it please be brutal, spelling, punctuation, grammer, concisness and precision are all fair game.
I don't care who the author is, should the guide become sticky, maybe a forum moderator should be the owner/publisher, allowing modification/revision as necessary in the future.
Again thanks for all your suggestion and insite.
The guide begins ----> see post 18 for the guide...
EDIT: removed guide for editing, I will revise and repost...
EDIT:EDIT: revised step #1 from start with just offending extension to use consoles
Instead of starting will all extension enabled, what about testing by enabling the offending extension and one other extension at a time? Wouldn't this help to identify quicker if two or more extensions were causing the behavior? (or multiple undesirable behaviors?) Also, is there a need to create a new "clean" campaign to do the testing in?
Sorry for the delay in responding. I wanted to think on this, get my thoughts in order. Lord Entrails, your idea is sound and a viable option. Actually one that the developer probably starts from to try to repeat the problem and then fix it. It's pretty much how I approached the issue. New campaign, load offending (my) extension and check for the issue reported by the user. Then add each of the extensions the user said he/she uses, one at a time, testing each time for the problem. Difficulty was I never observed the problem.Quote:
Originally Posted by LordEntrails
Whereas if we (the user) starts from where they observe the problem, the "dirty" environment, and works "backwards" until the issue disappears, we'll arrive at the same solution, the interacting extension.
Thank you for your thoughts, they helped me deduce step one in the "guide" is wrong. First, it may actually be detrimental to finding the problem, since it will take the user closer to the "clean" environment. The user might muddy the waters by changing settings and not just extensions that are necessary for the problem to exhibit itself. Second, if the offending extension is the only issue, I.e. there is no negative interaction of extensions, then step two will eventually get the user there anyway. They'll remove one extension at a time until they only have the offending extension left.
I am going to remove the guide from post #13, edit it and repost.
@Minty, good thoughts and I don't disagree. IMO, we need more of these documented solution/processes for issues we get asked in the forums regularly.
I couldn't agreed with you more. A perfect example of non-centralized, unorganized information is the Par5e threads. There is some really good information there for a really good application, but trying to ferret it out is, well frustrating to say the least, if not impossible. I've considered undertaking that as a project, distilling info from nosie, but I don't think I have the expertise with Par5e nor the stomach for it.Quote:
Originally Posted by LordEntrails
I think a community Wiki is the way to go. (I'm assuming I don't have Wiki privileges, I haven't tried.)
As stated previously, if you decide to critique this guide please be brutal. Everything is fair game, spelling, grammer, conciseness, accuracy, understandability.
Revisions: rewritten step #1 (use consoles)
Revised troubleshooting guide, starts now...
How to Troubleshoot Misbehaviors when Using Multiple Extensions
It’s common for GMs to want to use more than one community extension at a time. As an extension user you might be using 4, 5 or even more extensions. A new one is released by an extension developer that piques your interest, so you download and install it. And then things don’t work out as you’d hoped. Maybe the new extension just doesn’t work or maybe, with it loaded, some of the other extension’s functionality misbehaves. This is an indication of negative interaction between extensions. Let’s call the new extension the “offending extension”.
The extension developer is going to need your help. In order to find and fix the issue the developer must be able to reliably repeat the problem. It is highly unlikely that as the developer was working on their extension they had the exact same environment, i.e. the same extensions loaded, as you, the extension user. Given your list of extensions that you use, the developer could load them all up in an attempt to repeat the undesired behavior. However there are probably many other settings, specific to each extension plus those of the campaign and ruleset that may have to be identical to your settings for the problem to exhibit itself. It is virtually impossible for the developer to divine all these settings. Hence the developer’s need of your assistance. They will need to know all the steps you took to make the misbehavior exhibit itself.
Use the Console
As stated above, it is imperative that the problem be reliably repeated. One must be able to follow the same steps and observe the issue time and time again. If not, it’s going to be nearly impossible for the developer to observe and fix the problem. Once you can reliably make the extensions misbehave invoke the FG console for every instance of FG, player and GM alike. There are several ways to do this (see the **footnote below). Keep an eye on the console windows, report any messages to the extension developer.Quote:
#1 - Turn on the console.
Isolate the Negative Interaction
Now you’ll need to remove one extension at a time, always keeping the offending extension loaded, until the problem can no longer be repeated. As you restart FG each time, make sure your consoles are running. The last extension that was removed, when the aberrant behavior stopped, we’ll call the “interacting extension”. Inform both developers of this finding. The developers might ask you for environment files like the db.xml and/or campaign.xml files. It is possible, that you’ll remove all the extensions but the offending extension, in which case negative extension interaction does not exist. Instead the offending extension is not compatible with something in your campaign or other settings. Inform the developer of this; he/she will surely ask for the additional settings files.Quote:
#2 - Unload extensions one at a time.
Isolate Multiple Interactions
Having followed step two above, the offending extension and some of the other extensions will still be loaded. With the offending extension still loaded add each of the non interacting extensions, one at a time, again checking each time for undesired behavior. This helps, but is not guaranteed to, eliminate the possibility of multiple interacting extensions. As you restart FG each time, make sure your consoles are running. If you do notice a second or third interacting extension notify all extension developers of these findings. Again you might need to share environment data.Quote:
#3 - Reload the non-interacting extensions.
True, this is a lot of work for the extension user, but the extension developer can’t fix their extension without all the information they need to reliably repeat the problem. Once they have that information they can effect remedies and you both get what you wanted, you the user a cool new extension and the developer, a trouble free extension that everyone enjoys.
(**) Invoking the console.
(a) Type /console in the Chat Window and press enter, or
(b) Type /console in the Chat, then drag it to one of the hot buttons at the bottom of the FG desktop, or,
(c) Add /console to a desktop shortcut. If you have a Windows desktop shortcut that you use to start FG, duplicate it and then right click it and choose properties. Add /console to the target field, it will end up looking something like this:
"C:\Program Files (x86)\Fantasy Grounds\FantasyGrounds.exe" /console
The console should always be running as you work through the troubleshooting steps in this guide. If you just exit to the FG startup window as you remove extensions (step #2 above) or add them back in (step #3) the console will stay up. But if you exit completely from FG and restart it, options (b) or (c) above may be more appealing than constantly retyping /console in the Chat.
Hi, I unloaded all of my extensions except yours and still got the same error:
[ERROR] Script execution error: [string "C:masterindexitem_id:link"]:6: attempt to index field 'list_category' (a nil value)
It happens every time i open the npc page or try to search npc by name.
The error doesnt show if the wildshape ext. is unload.
Any idea? Thanks!
Duplicate post: https://www.fantasygrounds.com/forum...l=1#post697307Quote:
Originally Posted by PandaGentil
Please do not post the same question in multiple threads.
Closing this thread since it is many years old.