With the ARIS Global Game Jam approaching, I’ve been thinking a fair amount about how I can be helpful for those participating. We’ve done a lot of jams over the years, and gotten a lot out of them. Lately, I’ve been hunting bugs, making tutorial videos, and updating documentation. As I get myself ready to jam, it also might be a good time to share a few hints and pro-tips with would-be AR game designers. The lists below have beginners in mind but also have tips for those with some AR design experiences under their belts. These ideas aren’t comprehensive, but are just a few of the things I have been thinking about regarding making cool things with ARIS. I’d be happy to hear back from readers what tips they have, which of these ended up being helpful or not, and what else they’d want to know along the way.
Hints and Walkthrough for the ARIS Beginner
- Get the basic conceptual model down first: Objects, Triggers, and Scenes
- Make a simple 3 stop tour to solidify this understanding.
- Use locks to make that tour unfold as you take it.
- Actually try this out in person, not just by tapping the map (unless that’s the actual format you intend).
- Make something of your own. Something really small but that carries some interest for you. It does not and probably should not have some real purpose in mind. You don’t need all that pressure the first time you make something.
- Watch someone else try your tour or first game out; notice the things that are obvious to you but totally opaque for them.
- When it comes time to make something a bit more in-depth, steal liberally.
Some More ARIS Pro-Tips
- Every once in a while, the editor freezes. Simply reload the browser tab to fix.
- Have different tabs of the editor open at the same time in separate browser tabs. Really useful for adding in media and getting links while doing other work.
- Make a new conversation for each interaction with the player. If you layer all of the interactions into a single conversation, it is confusing when you come back to it later and want to see the flow.
- Allow for your player to acclimate to the UI of ARIS
- Plaques scroll, but not everyone notices this.
- Navigation of a map is something many people have to learn when they first play ARIS games.
- Map titles can be used for instructions to the player rather than literally identifying what’s at a location.
- There are many ways to hand out items, not just putting items on a map.
- Plaques hand out items really efficiently.
- So do conversation lines
- Plaques, conversations, items, these are all metaphors. You can bend or break them to make new things possible.
- The Decoder (A UI tab in the Client) is an alternate way to use QR codes, and can make creative use of the environment. A player finds and enters information instead of scanning an image. The author writes that information where the random number is above the QR code trigger in the Editor.
- Multiple Scenes and using Quests are not novice tasks in ARIS. They will break your game if you do not have a strong grasp of how Locks work.
- Once an item is given or taken by other parts of your ARIS game (plaques, conversation lines, quest notifications, etc.) a summary of where your item is in use (small icons) will show at the bottom of the “Edit Item” interface. This can help you keep track of your game.
- A teeny, tiny bit of html can greatly increase the presence and fluidity of media in your games. Of course this is useful for text formatting, but there’s more too. With just a bit of code you can have autoplay video and audio in plaques, conversation lines, and even the description of your game. The code below works for audio, but there are other options, and a very similar version works for video. More info here.
<audio autoplay loop> <source src="http://arisgames.org/server/gamedatav2/10950/aris940d74d20534c562c6903f8ca65bce47.m4a"> </audio>
General Design Tips
- You are creating an experience for your players. This is the end goal, not successful assimilation of content into an AR container.
- Make sure you are clear on the type of experience you are creating: tour, scavenger hunt, data collection activity, interactive story, simulation, etc. Reflect on genre conventions and hits in that format.
- Use the device and the players’ surroundings in a complementary fashion. If there’s a building in your game it is sort of pointless to show them a basic image of the outside of that building when they are looking at the building from the outside themselves in real world (TM) detail.
- If your game involves walking, be conscious that this takes time and effort. There is only so much walking that players will consent to, and a small jump on a screen takes time to cover in real life. As with imagery, the act of going from place to place should play a meaningful role in your design.
- Focus on the quality of experience, especially what the player sees within 1, 5, and 15 minutes, rather than on covering a certain amount of content.
- Give your player a role to play. “What is it that is exactly the same about every single vacation you have ever taken? You.”
- At a minimum, a story has a beginning, middle, and end. There are lots of ways to add or describe the structure of a story. Following some is better than a list of undifferentiated information.
- Look to produce a Minimum Viable Product, the teeniest part of your design that could be put in front of another human in working form. Get feedback on this before going down the rabbit hole.
- Consider using a design board to help guide and track your teamwork.