Mongoose Traveler 2E sheet issues

The roll templates used in the sheet seem to hardcode some color choices. This results in the roll values (the results) being unreadable in Dark Mode on Roll20. The rest of the templates that I've seen look ok, but the rolls are unreadable. I'll try and include an image. I noticed that the sheet was updated 2 weeks ago so someone might know how to fix this. :-) I really prefer running in Dark Mode and, frankly, an rpg that's set mostly in space is cool in Dark Mode. :-) I thought I might try to fix this myself and found the sheet on github. But, I don't know how to test changes in a game. Or how to propagate changes once I'm satisfied that it all works. There are other minor issues that could be fixed listed on the github site. In addition to fixing the sheet, I noticed on the github site that there was a sheet for space ships. I don't see that sheet anywhere in use on Roll20. There's no option to create a ship or to use that sheet anywhere I can see. Does anyone know how to do it? If the ship sheet is not available, can it be made available? That would be appreciated too. Roll result in dark mode: Filling the box with that purple color is the problem. The numbers are very nearly unreadable - I can just make them out. If it were changed to just be an outline, rather than filing the box, that would work perfectly. When not in Dark Mode, it appears perfectly with no coloring: I thought this had to do with the way Dark Mode was implemented so I sent in a bug report to Roll20 but they said that the sheet was community written and the problem is there so, I'm writing here to get help, as well as having opened an issue on the github site.  So, if someone knows how to fix this, I'd appreciate it.

This is trickier to describe than it should be, because its a sheet old enough to need the legacy mode switched on. There are two methods but I'll only describe the sandbox version. First, download the html, css, and translation files from that github folder. Secondm go to custom sheet sandbox, create a new campaign and with a new campaign, enter JSPON settings: {     "legacy": true } Save it and load the game. Once in the game, you'll have a form where you can load HTML, CSS, and translations. Do that, and create a character. Now you are ready to start editing the files. You can make changes in any of the 3 files you have downloaded (probably only the CSS one). and then load that file again and see the changes update immediately. Start editing! Once you are comfortable with the changes you made, upload your files to github (that's a separate uisse - do you know how to do that?)

The sandbox is described here: <a href="https://cybersphere.me/custom-sheet-sandbox/" rel="nofollow">https://cybersphere.me/custom-sheet-sandbox/</a> Uploading files to the github is described here: <a href="https://cybersphere.me/publishing-sheets-to-github/" rel="nofollow">https://cybersphere.me/publishing-sheets-to-github/</a>

Honestly, I gave up programming about 20 years ago. Long story. But, this looks complicated because the sheet already exists, and has lots of pieces including translations and other files. I'd be afraid to change something and have it all blow up. Plus, things aren't exactly as described in that sandbox guide so that worries me more. I'll leave it to the "experts". GiGs said: The sandbox is described here: <a href="https://cybersphere.me/custom-sheet-sandbox/" rel="nofollow">https://cybersphere.me/custom-sheet-sandbox/</a> Uploading files to the github is described here: <a href="https://cybersphere.me/publishing-sheets-to-github/" rel="nofollow">https://cybersphere.me/publishing-sheets-to-github/</a>

If you have time, I'd appreciate it if you could describe what's not as described. I wrote those guides, but things change over time and I'd like to keep them updated. But only if you are so inclined.

I usually do post problems/issues with guides and Roll20 and whatever I encounter. I believe that things won't change unless someone points out the errors/problems encountered and I encounter a lot of errors/problems. Since I first started in computers, I've had a knack for finding bugs that others don't. I will say that the guide you wrote is well written, and is one of the better guides I've seen. I used to proofread documentation as part of my job so I've seen a lot. :-)&nbsp; I'm just not inclined to do the programming and changes to the sheet for a number of reasons. And documenting the changes to the guide would require my going through the steps to do the work. So, don't expect to see anything anytime soon. :-)&nbsp; I might feel differently at some point in the future, especially if I find a problem that negatively impacts a game I'm involved with. GiGs said: If you have time, I'd appreciate it if you could describe what's not as described. I wrote those guides, but things change over time and I'd like to keep them updated. But only if you are so inclined.