I've uploaded the source and mod .jar for OSCCraft, a forge-1.7.2 mod that output Open Sound Control messages for specific player and block-related events.
- Mod outputs player position data and block hit/destroyed events over OSC
- Built into the Minecraft Forge 1.7.2 framework and can be loaded as a standard mod
- Currently, output is simply hardcoded to "localhost:6666"
- Output namespaces for the initial release are just:
=> /osccraft/player <x> <y> <z> <pitch> <yaw> <player-id> <event-id>
=> /osccraft/block/hit <x> <y> <z> <block-side> <player-id> <event-id> <block-type>
=> /osccraft/block/destroyed <x> <y> <z> <player-id> <event-id> <block-type>
Player position (XYZ), rotation and player ID are output on each tick.
Block hit and destroyed messages include block location as well as player id and a limited block-type (just for a few major block types).
Block and player events are filtered to send to each Client (i.e. sent to localhost), though this can be easily tweaked in the source to show all client data to each client.
More updates to come. Any suggestions or comments would be appreciated.
Enjoy,
Rob
-------------------
rob hamilton
center for computer research in music and acoustics
stanford university http://ccrma.stanford.edu/~rob
I've uploaded the source and mod .jar for OSCCraft, a forge-1.7.2 mod that output Open Sound Control messages for specific player and block-related events.
Files can be found at: https://github.com/robertkhamilton/osccraft
Here are a few specifics:
- Mod outputs player position data and block hit/destroyed events over OSC
- Built into the Minecraft Forge 1.7.2 framework and can be loaded as a standard mod
- Currently, output is simply hardcoded to "localhost:6666"
- Output namespaces for the initial release are just:
=> /osccraft/player <x> <y> <z> <pitch> <yaw> <player-id> <event-id>
=> /osccraft/block/hit <x> <y> <z> <block-side> <player-id> <event-id> <block-type>
=> /osccraft/block/destroyed <x> <y> <z> <player-id> <event-id> <block-type>
Player position (XYZ), rotation and player ID are output on each tick.
Block hit and destroyed messages include block location as well as player id and a limited block-type (just for a few major block types).
Block and player events are filtered to send to each Client (i.e. sent to localhost), though this can be easily tweaked in the source to show all client data to each client.
More updates to come. Any suggestions or comments would be appreciated.
Enjoy,
Rob
-------------------
rob hamilton
center for computer research in music and acoustics
stanford university
http://ccrma.stanford.edu/~rob