10 posts
Posted 27 October 2012 - 09:08 PM
Proposal:
A fairly simple (yet very useful) idea occurred to me. Why not have computers (and turtles) that respond to 'voice'?
Features:
Now, by voice I mean chat. It could come in the form of a peripheral (a microphone, obviously) which could allow it to be shut off. Any computer with one attached and within range would get an event (much like a rednet broadcast) which would then have to be parsed by a program to be used. It should probably ignore all commands (any message beginning with "/") to avoid conflicts.
Examples:
The purpose of this is to make simple interactions with turtles or computer controlled bases while not needing to reach the console. A few examples of what programs could be made with this:
The first obvious one is that this should be one way communication. While adding a "Speaker" as well to print out chat messages might sound like a good idea, the potential for spam is just too much. Plus, that would almost make terminals obsolete.
Next is how much information should be included in the event. Pulling a username seems to be on the same level as pulling a block id. I think leaving the messages unnamed would make things more interesting since developers would need to be creative to tell one person from the next. Maybe an arbitrary "voice print" id so messages could be compared to each other. Distances (much like rednet) would be nice as you could design a gps system as mentioned above.
Finally, the last problem I thought of is conflicts with "chat" mods. Many servers use chat mods that limit who can hear which messages. Usually in the form of channels, such as team/guild channels. How to deal with this one, I honestly have no idea, as each mod can have any number of methods to do what they do…
A fairly simple (yet very useful) idea occurred to me. Why not have computers (and turtles) that respond to 'voice'?
Features:
Now, by voice I mean chat. It could come in the form of a peripheral (a microphone, obviously) which could allow it to be shut off. Any computer with one attached and within range would get an event (much like a rednet broadcast) which would then have to be parsed by a program to be used. It should probably ignore all commands (any message beginning with "/") to avoid conflicts.
Examples:
The purpose of this is to make simple interactions with turtles or computer controlled bases while not needing to reach the console. A few examples of what programs could be made with this:
- You walk into your base and type "lock" (or a passphrase) in your chat and a nearby, hidden console responds by closing your piston door.
- After setting up a quarry, you type "mine here" and using gps-type triangulation, a turtle finds its way to you and proceeds to execute its mining program.
- A scout turtle flies over head or underground passively listening, marking on its map where and what it heard from the players it is spying on.
The first obvious one is that this should be one way communication. While adding a "Speaker" as well to print out chat messages might sound like a good idea, the potential for spam is just too much. Plus, that would almost make terminals obsolete.
Next is how much information should be included in the event. Pulling a username seems to be on the same level as pulling a block id. I think leaving the messages unnamed would make things more interesting since developers would need to be creative to tell one person from the next. Maybe an arbitrary "voice print" id so messages could be compared to each other. Distances (much like rednet) would be nice as you could design a gps system as mentioned above.
Finally, the last problem I thought of is conflicts with "chat" mods. Many servers use chat mods that limit who can hear which messages. Usually in the form of channels, such as team/guild channels. How to deal with this one, I honestly have no idea, as each mod can have any number of methods to do what they do…
