Troubleshooting: Plutonium

From 5etools Community Wiki
Jump to: navigation, search

framless
v1.4.0

(after each step attempt to reproduce your error)

Check FoundryTools FAQ to see if your issue is listed.

Currently the following Modules generate errors or cause usability issues if installed and active concurrently with Plutonium.
(there are no current known incompatibilities)


1) Check Known Issues/Rivet & Plutonium and the Plutonium FAQ
2) Check your Environment (Browser/Version/Extensions/Foundry Version/Installed modules). The browsers / restrictions supported
Supported Browsers
MINIMUM REQUIRED BROWSERS:
Chrome : 80+
Firefox : 75+
LATEST VERSION BROWSERS:
Chrome : 83.0.4103.97
Firefox : 77.0.1



KNOWN PROBLEMS WITH BROWSER VERSIONS:
Chrome:
Brave; Avast; Edge are all offshoots of the base build for Chromium - they may work, but ... if you have issues, you will need to check against a current release of the main browser. If the issue does not persist on the current release of official Chrome... then you have found why they are not officially supported.
Firefox:
WaterFox is not supported. It runs on a dated branch of Firefox build
ESR release is also, NOT supported, it runs on version 60, which is lower than the minimum required version for Firefox. Consider switching to the default branch of Firefox.


3) Disable the Plutonium module and see if the issues persists
If does, its most likely not a Plutonium issue,
4) Check your extensions and attempt generate the issue with extensions off.
If you are using Rivet, make sure you're using the browser Rivet is installed within as the browser to access FoundryVTT as well.
If does not, it most likely is not Plutonium,
5) Re-enable Plutonium; and confirm you are using Plutonium version v1.4.0 & Rivet version v0.1.3 or better;
6) Confirm you are using a version of Foundry and the D&D or game system that is compatible.
7) Document your Environment (Browser/Version/Extensions/Foundry Version/Installed modules)
8) Begin Loading Modules back one by one and testing; if the error presents only with another module loaded; there is an interaction issue and you'll want to...
9) Check the console Error log (Ctrl+Shift+J or F12), console


if you see entries which are in red and reference plutonium.js ; take screen shots of the error in console.

Then fill out the following and attach the screenshot(s) (Console errors and the screen showing the error)


Confirm you've installed it correctly (https://wiki.5e.tools/index.php/FoundryTool_Install), have updated to CURRENT release, and have (where possible) modded your backend. Then gather information to ensure your issue can be addressed and avoid back and forth attempting to get such after the fact.

Refresh game/Clear Cache (Control + F5);

Disable Plutonium and see if the problem persists when it is not loaded.

... If does, its not Plutonium most likely; if it does not..

Check your Extensions (Turning off all your extensions)

We're looking for possible issues with browser extensions modifying or blocking site content
Begin Loading Modules back one by one and testing; if the error presents only with another module loaded; there is an interaction issue and you'll want to...


Check the Console Error Log

This is usually entered by hitting Control + Shift + J, or F12 consoles logs will look something like this;
Look for the entries which are red or yellow and have plutonium.js in their text
Console Errors
Console Errors


If such exists in the console log, take a screenshot of that.


Then copy and fill out the following; Report the error on 5eTools community Discord in the #Plutonium Issues channel, inside the Virtual Tabletop Channel.

**Support Request**
<Statement_of_the_issue(s)>
**Environment/OS**: (ie Self hosted on Windows/On S3 or The Forge etc)
**Browser (version)**:
**Extensions (Version)**:
**Foundry & DND system Version**:
**Modules Installed (Version)**: Example(1.0);
**Reproduction Steps**: <List_all_steps_to_generate_the_issue>

Include console log screenshot(s) (F12) attached to the support request AND make sure if its NOT YOUR error, ie you're reporting for someone else that you state that.