EC v0.7 Fatal Memory Violation Error Report

On 13th of July, I released version 0.7 of Elemental Correstialism to Steam.
Prior to that, at late night of the 11th, I was just done with finishing my cinematic and I wanted to rush and create the "Correstial Outpost". Why rush though? This is because I really want to finish Elemental Correstialism before the end of summer, so that I have actual free time to prepare for a new school year. I was planning initially to release v0.7 on 10th of July, but it kept being delayed, because everything I thought would go quick actually took a longer time.
Anyways, I started working on the dungeon. Before that, I've realized that there will be a main display object in the outpost world, that'll display directions for different positions and parts of the story. Because I was going to just add the outpost and not add additional quests, I've added a big monitor that displayed and said "coming soon in v0.8, waiting for more updates". I added it to the tileset of my mod and started working.
I worked on the dungeon for a bit, then went to sleep.
The following day, I worked a bit on the dungeon more and decided that I'll need to test it.
For that I've created an instance world and a dungeon world, then created my own mission to travel to that world.
The problem was... each time I traveled to the world I got a "Memory Access Violation" error. There was no more information in the log regarding the problem. This got me pissed, since I didn't understand what was happening, after re-checking thousands of times my dungeon configs and I've decided to finally dismiss this new feature and instead replace it with something I had in mind for a bit too - Weapon Packages.
During testing of my mod with FU before release, I got more serious errors. I fixed an incompatibility error, but I got 1 more additional Memory Access Violation error. This time, it happened each time I wanted to generate a random Oxygen planet.
Finally, since I am working on a trailer for Elemental Correstialism v0.7, while recording gameplay, after standing still on a random spot of my Gas planet, the game again crashed with this error.
I started thinking that this was more of an internal or my PC problem. In fact, my PC updated on the night to that day, so I was like "Windows Update broke everything, it'll be fine for others".
But I was wrong!
A person named licflagg on Steam made a discussion thread on my mod on Steam. It surprised me, not only because it was the first discussion that wasn't actually made by me, but also because there was a major bug that I had to rush and fix.
It turned out to be this exact Memory Access Violation error.
Then I started investigating the problem.
The first hour of me trying to fix the problem made me decide that it was probably me addressing my custom tileset in the wrong way. And this was partially true, but not the cause of the error in the first place. I looked into examples of other successful mods on Starbound to see how they do it and, indeed they did it the different way. So I changed all of my dungeons to do it that way.
Now it broke ALL of my dungeons using my custom tileset. Now I got these Memory Access Violation errors each time I tried generating a world.
This made me understand that the cause of the glitch is my own custom tileset itself.
I looked on the insides and found out that it actually had an incorrect number, telling how many objects this tileset adds. I forgot to add 1 to it, when adding my "coming soon" monitor...
Welp, I am glad the error was fixed.
Hopefully now I can finish my Correstial Outpost!