quinta-feira, 23 de maio de 2019

Solarus 1.6 Is Out, Progress On Ocean's Heart


Some of you might remember previous coverage of Solarus, the Free Software Zelda-like ARPG engine that comes with its own complete game creation suite and a pretty impressive palette of Zelda fan games already available under its wing. As of last December, version 1.6 has been released, and while the changes under the hood are too many to number (check the full announcement and changelog here), it is worth highlighting the package now includes a more varied amount of libre tilesets, meaning developers now have available a wider choice of default non-proprietary graphics to use on their own creations. While the community is still very much focused around Zelda fan-games and their respective copyrighted graphics, this is an important first step to attract more developers and spark future libre game projects.

The Ocean's Heart tileset, now part of the Solarus package.

One such project is Ocean's Heart, the brainchild of Solarus community member Max Mraz. The game follows a gameplay structure similar to classic Zelda games transported to a Viking age-inspired setting. It features an entirely original story and a beautiful pixelated tileset, which Max was kind enough to license under a Creative Commons license for integration with the Solarus suite. Upon completion it will become the first true libre Solarus-made ARPG in code and assets, which makes for very exciting news.



Stay tuned for further developments on this, and be sure to check the Solarus website for news on their upcoming game projects, along with complete instructions and tutorials on how to create your own game using the development tools.

Code License: GPLv3
Assets License: Mixed  (most sprite packages copyrighted by Nintendo, original Solarus assets under CC-BY-SA)

The Inspirations Of Oceanhorn 2: Knights Of The Lost Realm - Part 1

The best thing about being a small team of developers is that we get to come to work and exchange opinions on what games we played lately, what retro titles our colleagues should check out, and what we could learn from the design of this or that game.


By popular demand, we decided to go over some of the games we think had some influence on our work for the Oceanhorn series, and in particular on its newest chapter, Knights of the Lost Realm.

   


Our first guest is Miko, Cornfox & Bros Game Artist. "I work very closely with Heikki (Cornfox's Creative Director) to create the visual style of the game. I focus mostly on environment art, but have worked on other things as well," says Miko, "We're trying to capture the feel of the original Oceanhorn, but the transition to the new Unreal Engine physic-based rendering opened up new possibilities for the series."  




Knights of the Lost Realm sports a world inspired by quite many late-90s RPG games: in contrast to what came before, often set in a medieval world of knights and castles, here we have both technology and industrial elements seamlessly integrated into a "classic" RPG setting. Breath of Fire 3, Grandia and Alundra (all from 1997) are good examples of this style, where coal, electricity, and gritty backdrops are mixed with classic RPG stuff.






"The world of Oceanhorn 2 is not completely industrialized, and in most areas it doesn't go as far as many of the environments do in FFVII, for example." continues Miko, "We are big fans of this classic though, and one can most likely see the influence Midgar had had on Arcadia's capital, the White City. Like Midgar, it has a circular design and you can see gigantic pipes rising over the walls of the city, but unlike Midgar it's not a dystopia. The White City is a beautiful and bright place, where the sun is always shining. In a way, we try to bring the scale of things to a level similar to what you see in FFVII: even if we use a different aesthetic approach, you feel like you could easily just walk on the pipes."



The more advanced technology in Oceanhorn 2 quite often have rounder and smoother shapes, much like some of the vehicles found in Akira Toriyama's work. The Yellow Bird, Trin's airship, is the perfect example of this rounder design. The most advanced Arcadian tech takes this up a notch, featuring an even sleeker and aggressive design, inspired by modern sports cars or jet planes.


"And then we have the Living Fortresses," says Miko, "compared to the original Oceanhorn, we had a bit more technical freedom with the art, so we tried to make them look even more sophisticated and dynamic. If the Living Fortress in the first title was our version of the Metal Gear Rex, the Living Fortresses in Oceanhorn 2 are an evolution on that, Cornfox's Metal Gear Rays."


If you want to know more about the games and styles that inspired us during the development of Knights of the Lost Realm, stay tuned for Part 2!

Journey: Won! (With Summary And Rating)

The winning screen you've been desperately anticipating for 8 years.
           
Journey
United States
Infocom (developer and publisher)
Released in 1989 for DOS, Amiga, Apple II, and Macintosh
Date Started: 20 March 2011
Date Finished: 21 May 2019
Total Hours: 23 (including 9 in 2011)
Difficulty: Hard (4/5)
Final Rating: (to come later)
Ranking at time of posting: (to come later)
              
Yeah, this one requires some explanation.
           
I was sitting around the other night trying to decide what game to play with the couple hours I had available. I had made some progress with Kingdom of Syree but wasn't loving it (it's another Ultima clone), and I was holding out hope I could dispense with it in a single entry. The self-imposed deadline for my next entry was looming and it didn't look like I'd be able to win that fast. At the same time, I wasn't keen to start on a complicated game like Darklands. So I did a quick scan of all the games I'd skipped and abandoned over the years to see if I could find a quick win. House of Usher (1980) looked promising, then The Amulet (1983), but both ended up as "NP" (and on my "Missing and Mysterious" list) when I couldn't get them to emulate.

My eyes then fell on Journey, an adventure game that I blogged about in 2011. By the time I was a few hours into it, I realized it wasn't even really an RPG (and MobyGames has since removed that designation). But I'd numbered and rated it anyway, so its loss was counting against my statistics. I began to wonder what the problem was. How hard is it to win a freaking adventure game? Why would I have abandoned it? Was I too proud to get a hint? How long could it possibly take to turn this loss around? That last question was particularly important because, as often happens, at this point I had spent longer trying to find a "quick win" than it would have taken me to just play a regular game.
          
Infocom called this a "role-play chronicle." What does that even mean?
           
I read my first and second entries from 2011 and began to remember the title, as well as the core problem: you have to reach the endgame with a sufficient number of reagents still in your possession, or you can't cast the final spells necessary to win. Since there are a fixed number of reagents to find during the game and plenty of opportunities to use them, you can put yourself in a "walking dead" situation as early as the first 5 minutes and not know until you reach the end, two or three hours later. I was apparently so disgusted with that prospect that I refused to re-start and took the loss. I was more willing to do that in 2011 than I am now.

So I restarted Journey with a willingness to play it through a couple of times if necessary, and it wasn't long before my "quick win" had taken over not just my few allotted hours but rather the entire afternoon, evening, and night until about 03:00. During this time, I restarted not once or twice but about 30 times, filled pages with notes about cause and effect, broke down and consulted two walkthroughs and still couldn't win because the walkthroughs were wrong, and finally--14 hours after I started--ended up with the set of actions necessary to get a party from the beginning to the end. And make no mistake--there really is only one.
           
In case you forgot, Journey is the game that canonically establishes that orcs and grues are the same thing.
          
By the end, I had a much clearer picture of the game than I did in 2011, and I reached an obvious conclusion that I'm surprised I missed back then: this is the worst adventure game ever made.
           
Journey hides this fact with nice graphics and typical Infocom-quality prose, but the game's approach is all wrong--fundamentally an insult to anyone who cut his teeth on both text adventures like Zork and graphical adventures like King's Quest. Every option it suggests is a complete sham, every hint of an RPG influence a complete farce. And its story isn't even that original--so much is lifted from Tolkien that he ought to have a co-author credit.
           
I feel like I've seen this somewhere before . . .
         
Journey (whose subtitle of The Quest Begins exists only on the box, not the game screens) tells the story of a ragtag band of village peasants who set off on a quest to determine why their crops have failed and their water has gone foul. A better-equipped, better-qualified band, led by the village blacksmith, Garlimon, left the same village the previous year and was never heard from again. This new effort is headed by the village carpenter, Bergon, and includes a wizard named Praxix, a physician named Esher, and a young apprentice food merchant named Tag. The game is mostly told from Tag's perspective, and the game lets you rename him in its one nod to RPG-like "character creation."
            
The party later finds Garlimon insane and living as a hermit.
             
The title differs from previous Infocom outings in that you do not type any of the commands. Instead, you select them with the arrow keys from an interface that distinguishes between high-level party commands (most of which move you to a new place or situation) and micro-level individual commands, aspected to the skills and abilities of each character. Thus, the party leader, Bergon, can almost always "Ask for Advice." Praxix has a perpetual "Cast" option, and Tag has most of the inventory options. I find the interface inoffensive, but not as revolutionary as the developers were clearly intending.
            
Some of the options in dealing with a party of orcs.
         
The party's initial quest is simply to find their way to a powerful wizard named Astrix who lives on Sunrise Mountain. Once they arrive, Astrix explains that the land is being threatened by the return of the Dread Lord, and he gives the party a quest to find seven magical stones. They must first find four (Nymph, Wizard, Dwarf, and Elf), which will lead them two others, which will lead to the final one, called the Anvil. Astrix believes that the stones are the key to defeating the Dread Lord. In their quest to find them, the party has to negotiate with dwarves, befriend elves, defeat bands of orcs, and explore ancient tombs. In these adventures, they make use of the special skills of several NPCs that swap in and out of the party.
             
Astrix gives the party its final quest.
          
If they recover the first six stones, Astrix tells them to seek the Anvil on the Misty Isle. The party must travel to the port city of Zan, dodge agents of the Dread Lord, and convince a captain to take them to the Misty Isle. Praxix has to cast some spells to help the ship navigate. Eventually, the ship crashes on the island and the Dread Lord attacks. Praxix is knocked unconscious, and Tag must figure out how to mix the right reagents to call a lightning bolt and smite the Dread Lord.
             
Tag saves the party in the final combat.
         
Just about every episode has some Tolkien source, though mercifully not in the same order as The Hobbit or Lord of the Rings. There's a dwarven mine that recalls Moria and an escape that not only feels but also looks like the bridge at Khazad-dûm. Another moment recalls the discovery of Balin's tomb. A ranger named Minar joins the party early on in an Aragornesque episode. There are echoes of Gandalf in Astrix and of Bilbo in the initially-hapless but ultimately-competent Tag. There's an episode that mirrors the Fellowship hiding from evil crows, and a tense episode in a tavern at the end that recalls the hobbits in the inn at Bree (the solution even involves turning one of them invisible). There's a Tom Bombadil-like figure named Umber whose nature remains a mystery until the end. The Dread Lord is, of course, an exact analogue of Sauron, and the stones are the game's equivalent of rings.
             
Crebain from Dunland!
Tag, just like Frodo, freaks out when he sees some suspicious characters in the Prancing Pony. If they stay at the inn tonight, the party will be killed.
           
The whole thing is reasonably well-written and would make a serviceable young adult novel, but as a game, it's nothing but endless frustration. Here is a small list of its sins:

1. It is completely linear. The one saving grace of difficult adventure games is that they are rarely linear. Usually, you can move back and forth between locations and solve puzzles in a variety of orders, taking the time to figure out what must be done in each place. Journey subverts this tradition entirely. You have to choose the right options the first time you arrive in a new location or you cannot return. For instance, there's one castle where you have the option to go to a left room or a right room. If you go to the right room, you see a chest full of jewels. If you're not exactly sure what to do there and leave the room, you can never enter it again. This happens repeatedly throughout the game.
         
The second screen invites you to enter a tavern or "Proceed" down the street. In any other adventure game you've ever played, if you proceed down the street, you can later turn around and go back to the tavern. Not here. Hit "Proceed," and you're out of town and on your way. It's pretty easy to hit some of these options accidentally, by the way; one too many ENTERs while scrolling through text will accidentally activate the default option on the next screen. An "undo" option could have helped a lot.

2. A "Back" option doesn't really take you "back." Most screens have a "back" option, and sometimes this returns you to a previous screen so you can choose a different direction. But much of the time, it serves as simply another way to go, usually one-way.
         
A simple choice to go left or right has enormous consequences for the rest of the game.
      
3. You're almost always walking dead. As I previously mentioned, if you don't reach the end of the game with the right number of spell reagents, you can't win. It is very easy to miss some of the reagents that you might otherwise pick up along the way, and also very easy to accidentally burn too many reagents casting spells. One of the options that burns too many reagents, by the way, is asking the wizard to "Tell the Legends" of magic. Usually, the "Tell Legends" option produces some useful lore about the game world, but if you ask him about magic, he does a little magic demonstration as part of his tale, which wastes necessary reagents.
           
The reagents are the most egregious example, but there are plenty of others. Fail to purchase a map early in the game--a map that the shopkeeper himself encourages you not to purchase--and you can't find your way to Astrix. Fail to ask a dwarf companion about some elf legends at the right time, and you don't have the right words to speak to an elf woman and thus miss your chance to get the Elf Stone. Fail to do a number of things just right in an early encounter with a nymph and you miss the Nymph Stone. Fail to accept a suspicious character into the party early in the game, and you miss later encounters because you don't have his scouting skill.
         
The shopkeeper tells you that a required inventory item won't help you.
          
Not only does the game give you no warning when something like this happens, but lots of other things happen that seem like they might be mistakes. In particular, party members disappear, get lost, get wounded, and even die on occasion, and you feel like you need to reload--only to discover, 20 turns later, that you can find or heal them in a different location.
         
4. Some of the walking dead criteria make no sense. Except in a single place where the dwarf Hurth has to "die" (or seem to die) only to be found alive again later, no character can die in a successful game, even if that character is no longer needed. This particularly bit me towards the end, in the city of Zan. If you don't do the exact sequence of events correctly in several locations, the Dread Lord's thugs are able to find your party and kill Hurth before the rest of the party members can escape. Even though Hurth's skills are no longer needed for the rest of the game, his death prevents you from winning.
       
5. Not only do you get no notifications of walking dead situations, a lot of text is wasted in such situations. It feels like fully half of the game's text would never be seen by a party destined to win because such text only appears when the party is already walking dead. There are entire areas of the game that, if you enter and experience any of the adventures to be had there, you've already gone the wrong way and cannot win.
          
A lot of text and programming--not to mention the graphics--went into a battle you're not even supposed to fight. You're meant to take a different path.
         
6. A lot of the options are completely nonsensical. Basically, on every screen, at every option, and at every encounter, you have to try every potential option and note the result--keeping in mind that its implications might not be fully realized for several scenes--and then try to assemble the "best" list of options in the right order. Some of the "successful" options you'd never hit upon by logic alone. Most involve the use of spells. For instance, Praxix encounters a stump on the ground in his explorations. If he casts "Tremor," the stump splits and reveals a passage into the Earth. It's both nonsensical to assume (without any other evidence) that such a passage would be revealed, and that "Tremor" would be the spell to reveal it. Later, you have to use the "Wind" spell in a random cave to reveal a hidden rune. Other encounters force you to discern at the outset whether you can cast a regular spell or need the extra "oomph" that comes from mixing the regular spell with grey powder, only the game has given you no gauge to determine the normal strength of spells.

7. The game randomizes some variables. Even if you can make an exhaustive list of the "right" options in the "right" orders, you'll still lose the game because each new session randomizes some of the variables. The most obvious is early in the game, when you're trying to navigate the paths to get to Asterix's tower. There are six choices of left or right, or 64 possible total paths, and you don't know if you've chosen right or wrong until you arrive. Each new game generates a different combination of correct paths. Now, technically you can bypass this navigation by casting a "Glow" spell on the map you hopefully purchased in the first town, but after a few sessions of this game, you're so paranoid about conserving reagents that you're more likely to sigh and start working your way through all 64 possible combinations.
           
The name of the boat captain you need to ask for at the end of the game is also randomized.
           
One of the things that the game randomizes is the color of the reagents that correspond with the different "essences": wind, fire, water, earth, and so forth. At the end of the game, Tag has to figure out what reagents to mix, and only a throw-away line in an earlier scene about brushing some color of powder from his hands keeps him from, again, having to reload multiple times and work through dozens of possibilities. 
           
Failing to note the "fine orange residue" early in the game makes it nearly impossible to cast the final spell.
         
The one nod the game makes to its own difficulty is by letting you view Tag's "musings" once you've lost the game. This screen lets you go one-by-one through all the things you did wrong, but only those things that led to your particular demise, and even then it's maddeningly vague with advice like "conserve reagents," not "you used reagents when you didn't have to in this specific place."
              
Tag muses on the many things the party did wrong.
         
Given all I've described, I have to highlight this particular paragraph from the game manual:
             
Your Journey will provide you with many hours of enjoyment and many hundreds of difficult decisions. But unlike other games you may have played, there are virtually no dead ends. Any action you take will advance the story toward one of its many endings. But there is only one ending that is the best.
          
I've never read such a blatant lie in a game manual before. There are no "alternate" endings--every single ending except the victory screen above has the main character reflecting on the literal destruction of the world. And the only way it can say that "there are virtually no dead ends" is because the damned game lets you keep on playing as long as possible even when you're in an unwinnable situation. That's not a virtue!
          
"Not a dead end."
        
These various failings are why it took me ultimately 23 hours to win a game that only lasts about 1 hour if you hit all the right options. And that's with using walkthroughs to help in some areas. With Journey, what you basically have is a cruel Choose Your Own Adventure book that you have to read 25 times, each time getting maybe an extra paragraph. It's barely a "computer" game, and of course certainly not an RPG. It has no character development, hardly any inventory, and the combats are all scripted.
          
The most frustrating part is, I'm the only one who sees how bad this is! In the June 1989 Computer Gaming World, Roe Adams--Roe &@&$*# Adams!--practically wets himself, calling it "the best effort to date of any game designer struggling to find a new way for the game to interface with the player," although he does caution about the use of reagents and mentions some of the more illogical puzzles. He seems to have been seduced by the interface--which is innovative but not all that great--and the plenitude of the graphics. European Amiga magazines gave it in the 80s and 90s.
       
Only more modern reviewers have failed to be lured in by its promises. In 1998, All Game Guide rated it a 40, called it "shallow," rejected its RPG credentials, and said that "it fails to take advantage of what a reactive computer can do that a non-reactive book cannot."
           
When I got done typing all of this and started searching for other modern takes on the game, I was delighted to see that Jimmy Maher ("The Digital Antiquarian") had covered it in 2016. As I read his piece, he at first scared the bejesus out of me by calling his initial reactions "a unique and very pleasant experience." But his opinion evolves as he plays, and eventually we get to the good stuff:
        
[T]here inevitably comes a point when you realize that everything Infocom has been saying about their game and everything the game has been implying about itself is a lie. Far from being the more easy-going sort of text adventure that it's purported to be, Journey is a minefield of the very dead ends it decries, a cruel betrayal of everything it supposedly stands for. It turns out that there is exactly one correct path through the dozens of significant choices you make in playing the game to completion. Make one wrong choice and it's all over. Worse--far worse--more often than not you are given no clue about the irrecoverable blunder you've just made. You might play on for hours before being brought up short.
        
When I rated it in 2011, I gave it a 23 without even bothering to explain the GIMLET. I don't know what I was thinking with some of the ratings. I gave it 2 points for "character creation and development" when it deserves 0 and 4 points for "magic and combat" when it deserves maybe 2 (some of the uses of magic to solve puzzles are at least well-described). A revision brings the score down to 17. It does best in the "game world" (3) despite being derivative, and in the graphics, which are credited to Donald Langosy. I agree with Adams that they're well-composed, and the game didn't skimp on them: practically every scene has a different set. 
          
Evocative graphics are one of the game's few positives.
          
The most surprising thing about Journey is that it was written by Infocom-founder Marc Blank, author of the original Zork series as well as the Enchanter series and several other Infocom titles. It certainly has his quality of prose, but it's hard to believe that he didn't understand why the basic approach was so much worse than the open-world games for which he was famous. Maher's account of the game's development suggests that the developers were in love with the interface: "an experiment to find out whether you could play an interactive story without having to type." There's nothing wrong with that, but it doesn't explain why the interface had to so relentlessly drive the player forward, to punish him so severely for minor mistakes, and to waste so much of his time in unwinnable scenarios. Fortunately, it didn't begin a trend. I like to think that Blank himself was dissatisfied with the result, which is why we saw no more games in the "Golden Age Trilogy," as the secondary title screen has it. 
                
I like to think that the next two would have been Destination and Return.
           
So there it is. In an attempt to get a "quick win," I managed to waste a lot of time and get myself highly frustrated on a non-RPG, for no benefit except to increase my "win" percentage by 0.31%. This does not bode well for an eventual return visit to, say, Wizardry IV, but we'll see.
        

People Behind The Meeples - Episode 170: Brett Picotte

Welcome to People Behind the Meeples, a series of interviews with indie game designers.  Here you'll find out more than you ever wanted to know about the people who make the best games that you may or may not have heard of before.  If you'd like to be featured, head over to http://gjjgames.blogspot.com/p/game-designer-interview-questionnaire.html and fill out the questionnaire! You can find all the interviews here: People Behind the Meeples. Support me on Patreon!


Name:Brett Picotte
Email:bubbamaker&$64;aol&$46;com
Location:Willard, MO USA
Day Job:President of Brettco, Inc.
Designing:Over ten years!
Webpage:www.pushfightgame.com
BGG:Push Fighter
Facebook:Push Fight or Brett Picotte
Twitter:@BPicotte
Find my games at:My webpage is the only place right now.
Today's Interview is with:

Brett Picotte
Interviewed on: 1/11/2019

Brett Picotte is both a game designer and an inventor. In addition to designing the game Push Fight, Brett also has a few inventions to his name, including practice golf balls and a Jiu-Jitsu training dummy. Read on to learn more about Brett and his projects!

Some Basics
Tell me a bit about yourself.

How long have you been designing tabletop games?
Over ten years!

Why did you start designing tabletop games?
I created a game for just for myself, one that I could play solo or with others. I had a need.

What game or games are you currently working on?
Push Fight for 2-4 players.

Have you designed any games that have been published?
Yes, Push Fight was published briefly by Penny Arcade.

What is your day job?
President of Brettco, Inc.

Your Gaming Tastes
My readers would like to know more about you as a gamer.

Where do you prefer to play games?
Family gatherings.

Who do you normally game with?
My nephews.

If you were to invite a few friends together for game night tonight, what games would you play?
I have a couple of games I invented by can't mention yet.

And what snacks would you eat?
Nachos

Do you like to have music playing while you play games? If so, what kind?
Yes - Beatles.

What's your favorite FLGS?
I don't have one.

What is your current favorite game? Least favorite that you still enjoy? Worst game you ever played?
Golf for all three questions. :-)

What is your favorite game mechanic? How about your least favorite?
Pushing is favorite. I don't have a least favorite.

What's your favorite game that you just can't ever seem to get to the table?
Monopoly - still one of my favorites for sentimental reasons.

What styles of games do you play?
I like to play Board Games, Card Games

Do you design different styles of games than what you play?
I like to design Board Games

OK, here's a pretty polarizing game. Do you like and play Cards Against Humanity?
No

You as a Designer
OK, now the bit that sets you apart from the typical gamer. Let's find out about you as a game designer.

When you design games, do you come up with a theme first and build the mechanics around that? Or do you come up with mechanics and then add a theme? Or something else?
With Push Fight, I came up with the board first. It had a theme, too - playing a game on a raft in the water. Losing meant taking a dip.

Have you ever entered or won a game design competition?
Never entered.

Do you have a current favorite game designer or idol?
No.

Where or when or how do you get your inspiration or come up with your best ideas?
I invent things that I need. I'm currently looking for a manufacturer for my golf practice ball.

How do you go about playtesting your games?
I play with family and friends.

Do you like to work alone or as part of a team? Co-designers, artists, etc.?
I like to work alone.

What do you feel is your biggest challenge as a game designer?
Getting it published by someone who wants to make it a huge success.

If you could design a game within any IP, what would it be?
A gambling game.

What do you wish someone had told you a long time ago about designing games?
Nothing really.

What advice would you like to share about designing games?
Have fun with it and don't expect to become rich.

Would you like to tell my readers what games you're working on and how far along they are?
Published games, I have: Push Fight
Games that will soon be published are: Can't say yet.
Currently looking for a publisher I have: If Penny Arcade doesn't produce anymore games, I will be looking for a new publisher.

Are you a member of any Facebook or other design groups? (Game Maker's Lab, Card and Board Game Developers Guild, etc.)
Yes, several groups. Abstract Nation is a cool one.

And the oddly personal, but harmless stuff…
OK, enough of the game stuff, let's find out what really makes you tick! These are the questions that I'm sure are on everyone's minds!

Star Trek or Star Wars? Coke or Pepsi? VHS or Betamax?
Star Trek, Coke, VHS

What hobbies do you have besides tabletop games?
Martial arts and sports

What is something you learned in the last week?
How to play Presbyterian Guitar by John Hartford on my guitar.

Favorite type of music? Books? Movies?
Rock and roll, bluegrass. Currently reading The Phenomenon (a book about Rick Ankiel) and just saw Bohemian Rhapsody. Great movie.

What was the last book you read?
The Phenomenon

Do you play any musical instruments?
Guitar

Tell us something about yourself that you think might surprise people.
I'm old

Tell us about something crazy that you once did.
Volunteered to be the first victim for the 5th ranked fighter in the nation at a karate tournament.

Biggest accident that turned out awesome?
Can't think of one.

Who is your idol?
Royce Gracie

What would you do if you had a time machine?
Go back to my high school and college days. Fun times.

Are you an extrovert or introvert?
Right in the middle.

If you could be any superhero, which one would you be?
Spiderman so I could shoot webs.

Have any pets?
Clyde the spoiled Coonhound/German Shepherd mix and Toby the cat.

When the next asteroid hits Earth, causing the Yellowstone caldera to explode, California to fall into the ocean, the sea levels to rise, and the next ice age to set in, what current games or other pastimes do you think (or hope) will survive into the next era of human civilization? What do you hope is underneath that asteroid to be wiped out of the human consciousness forever?
I hope Push Fight survives. And, it would save me a lot of time if my golf clubs got wiped out.

If you'd like to send a shout out to anyone, anyone at all, here's your chance (I can't guarantee they'll read this though):
Hello to all who love my game.

Just a Bit More
Thanks for answering all my crazy questions! Is there anything else you'd like to tell my readers?

I have an accounting degree and somehow passed the CPA exam. That's probably why I like the details of game design so much. I also invented a Jiu-Jitsu training dummy we call Bubba. I built Bubbas for a long time, and they are great for practice.




Thank you for reading this People Behind the Meeples indie game designer interview! You can find all the interviews here: People Behind the Meeples and if you'd like to be featured yourself, you can fill out the questionnaire here: http://gjjgames.blogspot.com/p/game-designer-interview-questionnaire.html

Did you like this interview?  Pleasse show your support: Support me on Patreon! Or click the heart at Board Game Links , like GJJ Games on Facebook , or follow on Twitter .  And be sure to check out my games on  Tabletop Generation.

Brainstorming With Reversal

In the previous two posts I described how I sometimes approach a problem by trying to arrange it into a matrix. Sometimes that doesn't work and I instead try to look at the problem backwards. As an example, consider procedural map generation. I often start with a noise function, adding octaves, adjusting parameters, and adding layers. I'm doing this because I'm looking for maps with certain properties.

Map of a procedurally generated island

It's fine to start by playing with parameters, but the parameter space is rather large, and it's unclear whether I'll actually find the parameters that best match what I want. Instead, after playing around a bit, I stop and think in the opposite order: if I can describe what I want, it might help be find the parameters.

This is actually the motivation I was taught for algebra. Given an equation like 5x² + 8x - 21 = 0, what is x? When I didn't know algebra, I would've solved this by trying a bunch of values for x, jumping randomly at first, then adjusting it once I felt I was getting close. Algebra gives us the tool to go in the other direction. Instead of guessing at answers, it gives me tools (factoring, or the quadratic equations, or Newton's iterative root finding) that I can use to more intelligently find the values of x (-3 or 7/5).

I feel like I often am in that same situation with programming. For procedural map generation, after tweaking parameters for a while, I stopped to list some things I wanted for the game worlds in one project:

  1. Players should start far apart on the beach.
  2. Players should move uphill as they level up.
  3. Players shouldn't reach the edge of the map.
  4. Players should join into groups as they increase in level.
  5. Beaches should have easy monsters without much variation.
  6. Midlands should have a wide variety of monsters of medium difficulty.
  7. Highlands should have hard "boss" monsters.
  8. There should be some landmark to help players stay at the same difficulty level, and another landmark to help players go up or down in difficulty level.

That list led to some constraints:

  1. The game worlds should be islands with a lot of coastline and a small peak in the center.
  2. Elevation should match monster difficulty.
  3. Low and high elevation should have less biome variation than middle elevations.
  4. Roads should stay at a fixed difficulty level.
  5. Rivers should flow from high to low elevation, and give players a way to navigate up/down.

The constraints then led me to design the map generator. This led to a much better set of maps than the ones I got by tweaking parameters like I usually do. And the resulting article has gotten lots of people interested in Voronoi-based maps.

Another example is unit tests. I'm supposed to come up with a list of examples to test. For example, for hexagonal grids I might think of testing that add(Hex(1, 2), Hex(3, 4)) == Hex(4, 6) . Then I might remember to test zeros: add(Hex(0, 1), Hex(7, 9)) == Hex(7, 10). Then I might remember to test negative numbers too: add(Hex(-3, 4) + Hex(7, -8)) == Hex(4, -4). Ok, great, I have a few unit tests.

If I think more about this, what I really am testing is add(Hex(A, B), Hex(C, D)) == Hex(A+C, B+D). I came up with the three examples based on this general rule. I'm working backwards from this rule to come up with the unit tests. If I can directly encode this rule into the test system, I can have the system itself work backwards to come with the instances to test. This is called "property based testing". (Also see: metamorphic testing)

Another example is constraint solvers. In these systems you describe what you want in the output, and the system comes up with a way to satisfy the constraints. From the Procedural Content Generation Book, chapter 8:

In the constructive methods of Chapter 3 and the fractal and noise methods of Chapter 4, we can produce different kinds of output by tweaking the algorithms until we're satisfied with their output. But if we know what properties we'd like generated content to have, it can be more convenient to directly specify what we want, and then have a general algorithm find content meeting our criteria.

In Answer Set Programming, explored in that book, you describe the structure of what you're working with (tiles are floors or walls, and the tiles are adjacent to each other), the structure of solutions you're looking for (a dungeon is a bunch of connected tiles with a start and an end), and the properties of the solutions (side passages should be at most 5 rooms, there are 1 or 2 loops, there are three henchmen to defeat before you reach the boss). The system then comes up with possible solutions and lets you decide what to do with them.

A recent constraint solver got a lot of attention because of its cool name and demos: Wave Function Collapse. You give it example images to tell it what the constraints on adjacent tiles are, and then it comes up with more examples that match your given patterns. There's a paper, WaveFunctionCollapse is Constraint Solving in the Wild, that describes how it works:

Operationally, WFC implements a non-backtracking, greedy search method. This paper examines WFC as an instance of constraint solving methods.

I done much with constraint solvers yet. As with Algebra, there's a lot for me to learn before I can them effectively.

Another example is when I made a spaceship where you could drag the thrusters to wherever you wanted, and the system would figure out which thrusters to fire when you pressed W, A, S, D, Q, E. For example, in this spaceship:

Example spaceship from a project of mine in 2009

If you want to go forwards, you'd fire the two rear thrusters. If you want to rotate left, you'd fire the rear right thruster and the front left thruster. I tried to solve this by having the system try lots of parameters:

Possible movements of spaceship

It worked, but it wasn't great. I realized later that this too is another instance of where working backwards would have helped. It turns out the movement of the spaceships could be described by a linear constraint system. Had I realized it, I could've used an existing library that solves the constraints exactly, instead of my trial-and-error approach coming up with an approximation.

Yet another example is the G9.js project, which lets you drag the outputs of some function around on the screen, and it will figure out how to change the inputs to match your desired output. The demos of G9.js are great! Be sure to uncomment the "uncomment the following line" on the Rings demo.

Sometimes it's useful to think about a problem in reverse. I often find that it gives me better solutions than if I only consider the forward direction.

quarta-feira, 3 de abril de 2019

The Argument Hour, With Seth And TC

I listen to a lot of game industry podcasts. 

Many of them are just people talking about games they like, or games they're looking forward to. There's never been a lot of design focused podcasts... a few have cropped up over the years, some better than others. I listen to the following pretty regularly that actually talk about the design of games:

Ludology

Board Game Design Lab
Building the Game
Game Designers of North Carolina

There are a few others as well, but I still always thought there was room for designers talking about the nitty-gritty of game design. I've always wanted to participate in something like that, but I didn't want to figure out how to do hosting and editing myself, and I would have wanted another voice to talk to (rather than just monologueing).

I mentioned something about this on social media a couple of months ago, and I got some interest from game designer, podcaster, and boardgame twitter personality, T.C. Petty III. Then Isaac Shalev of On Board Games contacted us, offering to edit and host such a podcast on On Board Games, should T.C. and I decide to record one.

And so was born The Argument Hour, with Seth and TC

The Argument Hour is a segment I've started doing with TC Petty III on the On Board Games podcast, where T.C. and I pick a topic related to board game design, and we basically argue about it for while. Then we do our twist on a game review. I don't like the idea of unilaterally saying whether a game is good or bad, so our reviews are more of a mechanical look at the game in question, and then our opinion on what kind of player that game would be good for.

We've done two episodes so far, and then went on a hiatus while I spent 6 weeks in the hospital while my new baby boy was in the ICU, but I hope we can get together again soon to record another one.

Episode 1 dealt with the "Alpha Player Problem" (whether it even exists), and included a brief review of Kingdomino.

Episode 2 was all about honing/returning to the well/designers revisiting ideas. The review that time was The Voyages of Marco Polo.

So if you read this blog, maybe you'd be interested in this. Give them a listen and enjoy!Leave a note here with comments and suggestions...