{"author_name":"triplefox","cat":"LD #17 - Islands - 2010","comments":[{"author_name":"hdon","time":"April 24, 2010 6:37 am","epoch":1272109020,"text":"What is the benefit? One down-side is that your identifiers would become invalidated if the actor’s position changed. Do you then have to propagate the new position to all actor identifiers?","spam":"N"}],"epoch":1272105540,"likes":0,"metadata":{"p_key":"71196","p_author":"triplefox","p_authorkey":"391","p_urlkey":"107017","p_title":"Pickup refactor","p_cat":"LD #17 - Islands - 2010","p_event":"LD17","p_time":"1272105540","p_likes":"0","p_comments":"1","p_status":"UPD5","us_key":"391","us_name":"triplefox","us_username":"\/author\/triplefox\/","event_start":"1271980800","event_key":"3","event_name":"LD17"},"text":"

I realized that my “tags” (integer identifiers on each actor) would benefit from being combined with their position data, rather than put off in a separate component.<\/p>\n

After another brief bug hunt(this one caused by there being two sets of identifiers for the player and pickup, one in the old tag code and one in the tile code) this is now working and the rogue-like collision, which I’ve made part of Fireball’s libraries, is that little bit more useful.<\/p>\n

Now, I should really stop dicking around with tech. I’ve got a game to write \":(\"<\/p>","time":"April 24th, 2010 5:39 am","title":"Pickup refactor"}