id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc	phab_field
782	Simplify RMS output format	Philip Taylor	historic_bruno	"The `texIdx2` in `tileData` is never used by the game and should be removed. (The one in `STileDesc` is never used and should eventually be removed too, but that'd break compatibility with .pmp files so it's probably not worthwhile until we have other incompatible changes that we can do all at once.)

I think it'd make more sense for `tileData` to be arranged by tiles, not by patches, and have the engine code rearrange as necessary. That'd make it easier to write RMS scripts from scratch, and would let us e.g. change the engine to have different-sized patches without having to change all the scripts too. (I think the .pmp files should be arranged that way too (I've wanted to experiment with the effect of patch size on performance and it's a pain with the current map format), but the same compatibility concern applies.)

The `isActor` flag doesn't seem particularly appropriate - there's nothing unique about actors, they're just entities whose template names happen to start with ""actor|"". There are other entities that e.g. don't have the `Ownership` component, so whether a `player` value is specified is conceptually orthogonal to whether they're actors. So I'd probably suggest getting rid of `isActor` and making the associated properties optional (defaulting to 0 or whatever)."	enhancement	new	Nice to Have	Alpha 5	Core engine