Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What needs to be done next? #116

Open
jarradbattaglia opened this issue May 30, 2014 · 0 comments
Open

What needs to be done next? #116

jarradbattaglia opened this issue May 30, 2014 · 0 comments

Comments

@jarradbattaglia
Copy link
Member

So as we leave the project there are some sections of the code that do need some retweaking.

First entity AI needs to be rebuilt. Currently we do not have a working AI system to control AI components. Currently it is very basic and only allows things to move in a straight path or attack when near an enemy faction.

Also currently the respawning system is having some trouble (I plan on fixing this before end of term). But if I do not get it fixed then go into "src/ayai/systems/RespawningSystem" for if a player dies and "src/ayai/systems/AIRespawningSystem" for enemies. This should not be a hard probelm to fix, just a little time consuming debugging.

The ECS system itself is prime to work with director level systems. If you want to create a global system, then follow the examples we currently have.

ART. Needs many more art assets that should have a 2D artist create new spritesheet. The way spritesheets are sent currently they are read from a file and need assign to a set of static commands (walkup, moveright, attackup). This should be refined either by sending a master file to the frontend, or changing how sprites are loaded through EntityFactory and create its own dedicated actor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant