Towns are loaded with corrupt special node data

[Nat Quayle Nelson]

Mentioned in the comments on my PR to fix inventory loading: #328 (comment)

entering VoDT or On a Ship to Algiers and taking a single step causes this error:

Unrecognized node type found: -256
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: -256
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: -256
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: 20480
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: 20992
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: 21248
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: -256
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: -256
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: -256
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: -256
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: -256
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: -256
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: -256
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: -256
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: -256
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Unrecognized node type found: 23552
        Note: This could indicate corruption in the scenario, but more likely is just a result of garbage data in unused nodes or in the memory structures they were read into. The unrecognized node type has been replaced with invalid type -1.Loading scenario graphics... ("/home/nat/.config/openboe/blades/Scenarios/On a Ship to Algiers/Algiers.exs")
./test.sh: line 1: 342298 Segmentation fault      (core dumped) "./Blades of Exile"

(Affects master branch)

[Nat Quayle Nelson]

The seg fault isn't happening anymore. Possibly the "corrupt" special node warnings were unrelated to the problem and don't need fixing.