{"author_name":"NicoM","cat":"LD #29","comments":[{"author_name":"Agreon","time":"May 13, 2014 1:40 am","epoch":1399963200,"text":"Hey!
\n Thanks for your article!
\n I think i am now ready to implement an entitymanager myself \":)\"","spam":"N"}],"epoch":1399938000,"likes":2,"metadata":{"p_key":"29862","p_author":"NicoM","p_authorkey":"32562","p_urlkey":"65328","p_title":"Entity Management","p_cat":"LD #29","p_event":"LD29","p_time":"1399938000","p_likes":"2","p_comments":"1","p_status":"UPD5","us_key":"32562","us_name":"NicoM","us_username":"nicom","event_start":"1398384000","event_key":"22","event_name":"LD29"},"text":"

So I’ve been making small changes and additions to what was my Ludum Dare basecode, and its getting to the point where I think it might actually be useful for other people. This begs the question: What do people actually need\/want in an entity\/component management system? Anything you can think of, please post in the comments, or tweet to me @nico_m__<\/a><\/p>\n

 <\/p>\n

Note that my system is for HaxeFlixel, and is already available on github<\/a>, the point of this post is just as a general question though, whether you use flixel or not, what would you want\/need in an entity\/component management system?<\/p>\n

 <\/p>\n

Thanks:),<\/p>\n

Nico<\/p>\n \n

Tags: component<\/a>, Entity<\/a>, Entity-Framework<\/a>, Flixel<\/a>, haXe<\/a>, HaXeFlixel<\/a><\/p>","time":"May 12th, 2014 6:40 pm","title":"Entity Management"}