​Receiving html instead of Character Sheet (IKRPG)

As discovered by Erdenshire T. , when using the IKRPG character sheet, all that is displayed is the html. Running down the list of bug reporting list: I am using Google Chrome I haven't dug into the extensions. I cleared my cache. The issue occurs when you open a character journal (character sheet tab), in a campaign using the IKRPG character sheet. Here is my support information The above is a screenshot. (this isn't a bug, exactly, and deals with a single character sheet, so I'm posting this is the character sheet section; I hope that is right) The word 'heartbreaking' comes to mind because of the work I put into it, and because how hard I found it to get the thing on github (the fact I was invited to a game that is suppose to be using said sheet is also a factor). The html on Github looks right, and I have the very same html in the custom section of my campaign. I am at a loss on how to fix this. Could on of those mighty Developers appear in a cloud in a cloud of brimstone and fire, flourish their items of power, and get this fixed?

It appears that your HTML file contains a Byte Order Mark (BOM). This is also true of the CSS file, which is causing the CSS to be thrown out entirely by Roll20's security check. (If you use developer tools to fix the HTML, it has no styling.) The BOM is an invisible character at the start of the file that is supposed to tell any program reading the file what encoding to use and the endianness of the characters in it. The BOM screws up Roll20's rendering. You will need to re-save your files without the BOM; the process to do this varies by the program you're using to write the files. The simplest way to do this will probably be to save it as ASCII (as opposed to UTF-8 or UTF-16 or Unicode or something), if you can.

Okay, I think I understand. The program I am using is just Notepad. I have saved the files as ANSI (they were formerly saves as Unicode, I think). Anyhow, files saved, committed, sync'ed, and pull request made. Hopefully, that fixes it. Thanks!

I can confirm that the version in the pull request does not have a BOM at the start of the HTML and CSS files. Assuming that's the only thing that was wrong (and I don't see anything else wrong), it should be fixed one the pull is merged.

Considering the first problem was referred to as an invisible character and you saw it...if you don't see a problem now, I'm happy.

You can see the character with a hex viewer, such as <a href="http://en.webhex.net/" rel="nofollow">http://en.webhex.net/</a> . Some text editors have the same capability. =) Current (with BOM): Pull request (without BOM):