02:10 <Rickmasta> Hey guys, would someone mind guiding me on how to "listen" to a specific user

02:10 <Rickmasta> for example, when it is that persons go in a game, and you want to listen for their response.

02:10 <Rickmasta> I've tried figuring it out, but can't seem to.

03:41 <leftylink> Rickmasta: it seems like the thing to do is just to listen to messages from any user, then just check whether it's the user you are expecting. if it isn't the user you care about, do nothing

03:41 <Rickmasta> So that's what I was doing

03:41 <Rickmasta> when it was their turn I set a "listeninguser" variable

03:42 <Rickmasta> but the issue I ran into was

03:42 <Rickmasta> how do I get it to wait around until the user says something?

03:45 <leftylink> Rickmasta: ah interesting. but isn't waiting around until the user says something the default behavior of cinch? for example if in a plugin I write "match 'hello'" then it's going to wait around until someone says '!hello', that's what you want, right?

03:45 <Rickmasta> yeah

03:45 <Rickmasta> but I'm not sure how to do it in the middle of a method

03:46 <Rickmasta> for example I have a method turn() and turn asks them to perform an action

03:46 <Rickmasta> I want to be able to capture what is said from inside method

03:54 <leftylink> Rickmasta: hmm, but it doesn't seem necessary for it to be in the middle of a method. because when you specify that a matcher should call a method, it's gotta start at the start of whatever method you told it to call...

03:55 <leftylink> Rickmasta: Iif I think abou tit, I could see a possibility to have turn() be running in a thread, it blocks on reading a pipe created via http://ruby-doc.org/core-2.1.0/IO.html#method-c-pipe , and then the message handler puts something into the pipe, but it seems a bit unnecessary. but i dont know, that's just me

03:55 <leftylink> the IO.pipe solution *could* work, but seems a bit "unnatural"

03:55 <leftylink> basically

03:55 <leftylink> that's what I think anyway

03:55 <Rickmasta> Gess I should have mentioned that I'm a novice programmer.

03:56 <Rickmasta> I have no idea what and IO.pipe is.

03:57 <leftylink> ah, then I guess it was a good idea for me to have linked to the docs on it then

03:58 <leftylink> ok yeah that explained it much better than I could have possibly hoped to explain it, phew

04:07 <leftylink> Rickmasta: so I think the logical conclusion of the "it's gotta start at the start of whatever method you told it to call..." to me is that turn() should actually be broken into two methods. the first part should ask the user what to do, that's it, it does nothing else. then when the user says what to do, that should cause the second method to get called

04:07 <Rickmasta> yup

04:08 <Rickmasta> thats what I'm doing

04:08 <Rickmasta> now just trying to figure out how to keep track of the user's choices