Welcome to round 1 of Architect
Join our community on the Architect Discord Server!
Have you ever wanted to make a game but ran into a wall when there was just too much you wanted to add at once? Has scope-creep ever left you burnt out? Have you struggled to just get yourself to sit down and code? Well Architect can help.
Architect isn't an ordinary game jam. Rather, it is a series of continuous, collaborative, unranked jams where you will build an entire game from the ground up. Starting on your first round and building it up over time.
On their first round, participants will create a basic game, it may even be as simple as just a rectangle that moves left and right on the ground. There is no need for art or gameplay yet.
On the next round they will think of one thing to add to the game, for example let's say allowing the rectangle to jump. And they will just refine and polish that feature across the two weeks.
Then the next round they will think of a new aspect to introduce, for example maybe spikes that the player must avoid. The point is that there are no long- term goals. The idea here is that every round your game is a complete product. It doesn't matter what you add, but there can't be anything unfinished.
When you code on your own, there are no guidelines other than those you set yourself. Scope-creep happens to everyone, and when you're working by yourself, it's all too easy to procrastinate coding until you give up altogether.
Architect is designed to build your game in slow increments. So, instead of scope-creep sneaking in and stopping you from ever finishing your game, your game will always be in a state of completion. You just get to add more each round.
These rounds can encourage you to actually work on your game by giving you a deadline to show progress. It means there's a reason to code beyond just your general desire to make a game which, if you're anything like me, sometimes isn't enough.
And of course that's not to forget playtesting. By building your game here you can have constant access to a community that can test, discuss, and critique your game.
No. There is absolutely no pressure to submit every round. If you want to take a break, if you don't feel like coding, or if you want to do another game jam instead, now worries. This is a 100% casual setting focused on helping you make the game of your dreams.
Your additions to your game don't need to be a lot. You could of course add a full movement system or an entire complex boss to your game. But if you don't have the time to work on it, you could add art or sound effects. You could just work on the level design. Or you could even just make a single NPC that can be talked to. As long as the game's complete, anything works.
And it's worth noting that you don't need to stick with one game forever. If you grow tired of the game you've been working on, but don't want to quit Architect completely. That's fine. Don't feel pressure to put time into something you don't like.
This is a casual space, so there aren't many strict rules, but there are a few to keep in mind.
-Keep It Finished: Whatever aspect you choose to add must be completely finished within the 2-week window.
-No AI Art or Code: All work put into your game cannot use any AI.
-Stick to the Clock: While planning during the breaks is encouraged, all actual work towards your game should wait until the jam actually starts.
-Be Respectful: Hateful, offensive, or discriminatory content will result in removal.
-Content Warnings: Make sure any potentially uncomfortable content is labeled as such.
-Playtest: This jam revolves around community, and playtesting is one of the best ways to help build an amazing game. As such, you are highly encouraged to play and comment on as many games as possible, and they are expected to do the same for you.
This is an experimental framework. The rules and logistics of future rounds will be adjusted based on community feedback.
