It was actually your entry that inspired me to write about this, Matt. =)

It doesn't need to be IRC, but my initial idea was to pick an existing chat
protocol for which servers and chat room names are freely available to
anyone.

Anyways, through such thing one could skip the "building the UI for
inputting peer IP addresses, talking about connection errors, negotiating
matches, making a chat room for the gamers" part of building a network game.

And as a bonus, that could result in an increase of network-capable pyweek
entries. I'd love to have my next entry for Pyweek be network-capable if I
can skip past through the "building the UI within a week" part. =P

-Thiago

On Sun, Sep 19, 2010 at 9:11 PM, RB[0] <[email protected]> wrote:

> Actually that sounds similar to a project I'm considering starting.
> During Pyweek we made a networked game, and were going to have a master
> server where you can register your own servers, and other can find them.
>
> It would be fairly simple to create and other games could use it...
> I wasn't thinking about using irc though.
>
> But yes, definitely sounds feasible...
>
> Matt
>
>
> On Sun, Sep 19, 2010 at 12:20 PM, Thiago Chaves <[email protected]>wrote:
>
>> Email vaguely related to my first one.
>>
>> How about coming up with a "Pyttle.net" client (and server) (and not with
>> that name), which would basically be an IRC chat that launches networked
>> games between people? Games that utilized it could register to the thing
>> locally so the chat knows which games you have that support it and the
>> client could launch the games with the appropriate command-line arguments to
>> get a game between people going. (or maybe "importing" the game and
>> launching it from withing the client, if there's a game skeleton provided)
>>
>> The server-side could also support assigning random matches and ladder
>> games.
>>
>> I've been reading Twisted documentation and this sounds like a
>> less-than-guru-level thing to build on top of the IRC protocol.
>>
>> Does it sound feasible?
>>
>> -Thiago
>>
>
>

Reply via email to