jmmk / clash-attack-sim Goto Github PK

Each building should have an unspawnable zone that is one tile bigger on all sides.

Currently it finds a target and decides what action to take

MVP

• Can place building on grid (large squares, no walls yet)
• Building cannot overlap another building

Non-MVP

Interface

• Separate interface for Play and Build that can be switched between
• Layout can be saved and played

Functionality

• Allow choosing one of many different buildings
• Limited number of each building
• Export Layout / Share Layout With Friends

• Which frames to run on (every 3, every 5, etc.)
• Which entities to work on (based on components)
• Function that returns a list of entities to associate (currently a custom list comprehension inside each system)

This would also allow adding/removing systems dynamically during execution

moving vs attacking would be a component and instead of the system checking the state of a component, it would only check for the presence of a component. The technique is outlined here: http://www.richardlord.net/blog/finite-state-machines-with-ash#more-1064

Chrome 43
http://jmmk.github.io/clash-attack-sim/

Got Error: Minified exception occurred;

Currently archers are implemented as a random chance to spawn on left-click. Instead, there should be a choice between spawning an archer or barbarian.

Right now I set one animation sequence for moving. The animation sequence keyed off state like :moving, :attacking, etc.

This should be standardized one way or the other

Currently using modulo of frame-count and an entity's attack-speed, but this makes all entities with the same attack speed attack at the same exact time. Instead, once they get in range, they should set last-attacked to the current frame-count. When frame-count equals last-attacked + attack-speed, attack again and set last-attacked to current frame-count.

With the addition of the attack and health system, performance is getting bad once enough entities are on the stage. Should research and implement basic performance enhancements

@param [options.roundPixels=false] {boolean} If true Pixi will Math.floor() x/y values when rendering, stopping pixel interpolation.

Currently it only allows one click per frame. It should be an array of all actions in a frame

New entity that shares the hp component of another entity and is positioned at top of it

CEASE DEVELOPMENT OF THIS GAME

You are infringing upon the copyrights of one Clash of Clans™© and you have been reported to the authorities.

SWAT TEAMS ARE APPROACHING YOUR LOCATION AS WE SPEAK
DONT FUCK WITH US

Seems like when adding an enormous number of barbarians, hp doesn't drop as quickly as it should

I should use an actual input queue instead of just a "click" queue. And when I handle each event, I will have more conditions to check