ctomni231 / cwtactics Goto Github PK

combine base selector function of units and properties to one

Player 2 and 3 cannot act, never. Player 1 can act if you do next turn to get to day 2.

slide up -> index--

slide down -> index++

There is a test inside Engine Bridge and Test Map describing the error. It leaves a bunch of error messages and does not load the JSON map properly. I tried it with the internal map in DetachedMapUtil.java and the 3 external json file maps each with the same errors.

• Action structure
• Serialized commands must be smaller
• Divide move from action as single command
• Better file structure

in weapons.json

This only produces many object creations and is not critical to have it. In many situations like Move we have only one card at the same time. In that case a single object in the root context should be enough for the requirements.

• it seems it only happens to the first unit type
• all properties have recolor problems

Confirmend on FF 17,18 and 19

• Sets type SILO_EMPTY to SILO

cwt.clearTargetSelection( centerX, centerY );

cwt.setTargetForSelection( x,y );

// INVOKES COMMANDS TO GET A SELECTED TILE FROM GAME CLIENT (ASYNC)
cwt.receiveTargetFromSelection();

Pictures are usually better than words. It doesn't affect how the item is selected, but it is a very small bug nonetheless.

from AWDS

• Player decision by click on an enemy unit or property
• Sub menu: amount of money 500, 1000, 2000, 5000, 10000, 20000, 50000

Seems the received path from astar do not recognizes units in the way. This must be fixed.

Furthermore the move logic does not set the positions correctly if the way is breaked.

• Template based sections

n.t.

1. SELECT MOVE TARGET
2. SELECT ATTACK ACTION
3. SELECT TARGET
4. SHOW WEAPONS AS SUB MENU

I think the shape of the rocket plus a flame would be enough

Sometimes it is still visible if you are in a situation where it is not usable like joining.

• New UI
• Tile and unit information about the selected tile

may an actionm fault or move type fault...

Some bad bugs that was a result of the refactoring. I think it would be nice for testers to have a working milestone 1.

• UP, DOWN
• ACTION, CANCEL
• Menu shifting via div.scrollTop

• Selected unit or property selects the unit that can be dropped
• Sub Menu: player decision

like a development diary ^^

less DRY ( in case of action names ) stuff should be needed to define actions.