Tokinsom

Yes, the moving angle is calculated by "object's current position and previous position".

You might store initial "moving angle" in private variable manually before moving.

Update

Fix a possible bug which might not load player.

sakurawar

Download this plugin and try again. Thank you for pointing out this problem.

joelarenaz

Sorry, I forgot updated the first post. Here is the new document page.

sakurawar

Could you provide a simple test capx?

Group 4 ( Capx, remember update related plugins)

• drag any chess on the board
• it will try to put 4 connected chess into a chess-set (miniboard)

Update:

Add rex_board_hexshapemap plugin to place hex grid with hexagon, triangle, parallelogram shapes.

Update

hexTx plugn: Fix bug about transferring logic XYZ to physics Y.

tilemap in "Acts.prototype.SetX = function (tilemap, zX)" is an "object type", not an "object instance".

the first parameter of "cr.plugins_.Tilemap.prototype.Exps.PositionToTileX.call(tilemap , fake_ret , zX);" should be "object instance".

So you could try

Acts.prototype.SetX = function (tilemap, zX)

{

var tilemap_inst = tilemap.getFirstPicked();

cr.plugins_.Tilemap.prototype.Exps.PositionToTileX.call(tilemap_inst , fake_ret , zX);

this.testing = fake_ret.value;

};

Breakout ( Capx, remember update my plugins. )

• like breakout, blue ball will bounce while hit any brick, and destroy brick
• drag and drop below bricks to the chess board
• game over while blue ball is running out of chess board.

Ashley

You are right, status will be reverted by the subsequent loading, except non-saved status.

For example, to count the playing time of this level:

Designer might increase playing counter which saved in localstorage/post to server while starting this level by "On start of layout".

When player continues the game by loading status, the playing counter will be increased again. It might be a problem, imo.

( Or private variables changing in sprite with no-save behavior... etc. )

Update:

rex_parse_itemtable plugin:

• Add "Action:Set itemID", and a new "Action:Save" to save item. Older actions like "Action:Save to itemID", "Action:Push", "Action:Save at first queried item" had been deprecated (these actions still could work).
• Add "Action:Add to queue", "Action:Save all" to save multiple items in 1 request. See document for more detail.

You might try this behavior