{"push_id":855129848,"size":1,"distinct_size":1,"ref":"refs/heads/feature/redstone-tracking","head":"09068c702758594d47dcb24dc5e55148e542642f","before":"3ce8a0ecdc153dfb3011aef99c5ef68d186ad014","commits":[{"sha":"09068c702758594d47dcb24dc5e55148e542642f","author":{"email":"93806af59f97199bdb7be810bcfd0c35fbb61999@gmail.com","name":"bloodmc"},"message":"Implement redstone tracking.\n\nThere are now 2 types of player tracking. The first is OWNER which tracks when\na player places a block. The second is NOTIFIER which tracks when a player\ninteracts or notifies one or more blocks.\n\nIn order to track redstone block changes, whenever a player performs an action\nthat causes one or more blocks to change, the tracker attempts to follow the\nflow and store the player's UUID index within each block position.\n\nConsider the following example :\n\n1. Player A places 10 crops.\n2. Player B activates some redstone setup which waters these crops\n3. The 10 crops begin to grow\n\nAt step 1, the only player information for the 10 blocks placed is Player A.\nAt step 2, the tracker notified all 10 blocks and added Player B as the\nNOTIFIER. At step 3, the ChangeBlockEvent would have both Player A and B in the Cause.\n\nNote: There are many scenarios for redstone, this commit is merely the first\nattempt at tracking most of it successfully.\n\n* Implement DestructEntityEvent","distinct":true,"url":"https://api.github.com/repos/SpongePowered/SpongeCommon/commits/09068c702758594d47dcb24dc5e55148e542642f"}]}