From: Dennis Payne <dulsi@identicalsoftware.com>
To: Paul Sutton <paulsutton@disroot.org>,
libreplanet-discuss@libreplanet.org
Subject: Re: Global Game Jam
Date: Sat, 01 Jan 2022 09:52:05 -0500 [thread overview]
Message-ID: <f19916f5e5afd8116d43c3fd740b7b636a99c7d0.camel@identicalsoftware.com> (raw)
In-Reply-To: <3aa1bbf9-c8e5-ca36-8780-b4c3ab3ed28b@disroot.org>
I mentioned on the FreeGameDev site that the game jam portion of
Liberated Pixel Cup was not a success and someone disagreed with me.
The problem was we had different definitions of success. I want games
that I can still play now and perhaps even see improvements. He looks
at it as they produced some interesting games.
You can see the same with the global game jam. It has produced
thousands of games. But I can't say I've played any of them. I'm sure
there are some great games in there but I don't know any that have
risen out of it.
As a game developer, I like game jams. I think a game jam associated
with LibrePlanet and have a session dedicated to showing off the games
would be fun. With two kids I've found it hard to participate in many
jams but I would like to do more. If one person plays my game and likes
it that a win for me (and that one person may even be me).
I just don't see a game jam significantly increasing the number of good
free software games. Maybe you can structure a game jam in such a way
to bring that about. FreeGameDev suggested maybe focusing on modding
games. The Linux Game Tome tried to get people to fix up a game for a
month. That lead to SuperTuxKart fork from TuxKart. However that effort
didn't really succeed and only became the success it is after it failed
and new developers resurrected the game. Could you do a game jam where
everyone builds level for a game and the best are worked together in
the end? I think it would be difficult to weave them together and not
have duplicate elements in the levels. But I think it might be an
interesting thing to try.
On Sat, 2022-01-01 at 12:01 +0000, Paul Sutton via libreplanet-discuss
wrote:
> Hi
>
> Following on from the suggestion of a Libre Game Jam, there is an
> event
> coming up
>
> https://globalgamejam.org/
>
> This appears to be along similar lines to what was suggested, so may
> be
> good for some ideas.
>
> Paul
>
>
> _______________________________________________
> libreplanet-discuss mailing list
> libreplanet-discuss@libreplanet.org
> https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2022-01-01 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 12:01 Global Game Jam Paul Sutton via libreplanet-discuss
2022-01-01 12:23 ` Paul Sutton via libreplanet-discuss
2022-01-01 14:52 ` Dennis Payne [this message]
2022-01-01 16:22 ` Paul Sutton via libreplanet-discuss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f19916f5e5afd8116d43c3fd740b7b636a99c7d0.camel@identicalsoftware.com \
--to=dulsi@identicalsoftware.com \
--cc=libreplanet-discuss@libreplanet.org \
--cc=paulsutton@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).