passiomatic / mage-city Goto Github PK

From the docs:

When you use the tile flipping feature added in Tiled Qt 0.7, the highest two bits of the gid store the flipped state. Bit 32 is used for storing whether the tile is horizontally flipped and bit 31 is used for the vertically flipped tiles.

To enable variation while editing levels it would be useful to support at least horizontal and vertical tile flipping (we can add diagonal flip later). Flipping bits should be extracted by elmify utility and possibly stored into the B channel of the LUT which is actually unused.

Then, shader would extract the bits and invert the final tile coordinated according to those values.

Note: I was assuming that WebGl 1.0 supports bitwise operations. It turns out this is not the case. However, since we need to test only two bits we can easily check against four hardcoded integer values (e.g. 0 = no flipping, 1 = flip h., 2 = flip v. and 3 = both h. & v. flip).

Allow to specify player start position for each level file, perhaps using the midpoint of a object named Player.

Since the player start position could be thought as a spawn point, we could put that player object into a specific layer, which contains all the information needed to spawn each entity in the game.

Discussion:
https://stackoverflow.com/questions/7615009/disable-interpolation-when-scaling-a-canvas/7665647#7665647

Relevant CSS:

canvas {
  image-rendering: optimizeSpeed;             /* Older versions of FF          */
  image-rendering: -moz-crisp-edges;          /* FF 6.0+                       */
  image-rendering: -webkit-optimize-contrast; /* Safari                        */
  image-rendering: -o-crisp-edges;            /* OS X & Windows Opera (12.02+) */
  image-rendering: pixelated;                 /* Awesome future-browsers       */
  -ms-interpolation-mode: nearest-neighbor;   /* IE                            */
}

WebGL's DepthTest is wrong when dealing with multiple layers. See attached screenshot. More generally, having these as entityWith settings:

entitySettings =
    [ DepthTest.default
    , Blend.add Blend.one Blend.oneMinusSrcAlpha
    ]

would make less as default depth test, with a value of 0 meaning closer to the camera and a value of 1 farther to the camera. This seems not to be the case, in fact it seems to work backward.

To avoid page scrolling problems use W, A, S and D keys for player navigation.

Relevant function: http://package.elm-lang.org/packages/ohanhi/keyboard-extra/3.0.2/Keyboard-Extra#wasd

Example using both WASD: https://ellie-app.com/35nZJ9mySNja1/1