Blank tiles

[SymKensaki]

I find when constructing set pieces, that I cannot use certain tiles like desert or deciduous.  They have a designation within constants, but inputting that number either results in an impassable tile, or something incorrect altogether.  I've tried putting in other numbers to see if perhaps it was just wrong, but again I am confronted with the same issue.

I was hoping to glean some information from other static layouts, but deciduous_pond is all zeroes, and hound_rocks is suspiciously covered in rocky terrain, despite only spawning in the desert.

 

Does anyone have any solutions to this issue?

[Kzisor]

Set pieces are not completely designed to be mod friendly. On August 6, 2015 I sent @PeterA a private message outlining this issue, with a fix for it. Unfortunately he has been extremely busy and has not had the opportunity to take a look at the code I sent him. Basically, the problem is in how set pieces were originally designed. They were designed with a static table, instead from using the constant values. So every time a new tile is added it would need to be added to this static table as well.

The solution I proposed is instead of only using the static table, have the ability to add a property to the ground tile inside Tiled. Upon loading a set piece check to see if this property is applied and if so use the tile based on the name. Hopefully in time @PeterA will be able to circle back around and implement my fix or a similar fix to help mod authors create more efficient set pieces.

 

[SymKensaki]

Nevermind, I'm blind.

 

Either way, hopefully something gets worked out eventually, then.

Edited March 4, 2016 by SymKensaki