{"push_id":701841010,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"1fb8c0216692aa9858e28cf697fff39c01e00f1b","before":"d8f8e2e2c4055617bd68753b0a60e3c9f39853dd","commits":[{"sha":"1fb8c0216692aa9858e28cf697fff39c01e00f1b","author":{"email":"a7ef40ae69c886a558abbc75cb5f3ad3129c1bcc@gmail.com","name":"Chris Maguire"},"message":"AI module, Logging, Attacking /w tests\n\nCreated an module for computer controlled entities called AI.\n\nAdded a logging module and converted all io:format and existing\nlog calls to use erlmud_event_log. The log functions automatically\nadd the module name and erlmud_event_log automatically adds the calling\nprocess' PID and--if found--the name of the PID registered with\nerlmud_index. erlmud_index allows looking up an ID or a PID.\n\nerlmud looks for the log path in $ERLMUD_LOG_PATH\n\nImplemented attacking:\n\nAttacking happens in several stages:\n1) find player\n2) start attack\n3) find target\n4) calculate \"hit score\" (i.e. did the attack land)\n5) calculate damage\n6) apply damage\n7) calculate wait time\n8) listen for message saying target is killed\n\nLike all actions in erlmud, each of these steps is a message sent out to\nall connected processes to either pass, fail, resend or modify. I've\nadded the ability to modify a message so that each connected process can\nmodify a value (e.g. hit score, damage amount) in a message. If the\nprocesses were to send a new message then everyone would see it again.\nThis way processes only need to see the message once BUT they cannot\nreact to changes in the value as they have no guarantee which changes\nthey'll see: i.e. the first process to add an amount to the \"hit score\"\nwill not see any subsequent changes.\n\nCurrently the attack will cease if something decides that damage cannot\nbe applied, so this shouldn't be used.","distinct":true,"url":"https://api.github.com/repos/cwmaguire/erl_mud/commits/1fb8c0216692aa9858e28cf697fff39c01e00f1b"}]}