Now that I have more experience, I find it’s easier to take risks and make assumptions about the players I want to target.

Like if I were to make a card game, I’d assume my players know how energy/mana works.

I’m like that. I start from the assumption, “my player has never used a gamepad before.”

This started when I read this one article, I gotta find it again, but it changed my perspective on how to teach players when they play my games.

A fundamental common denominator.

Or also how on the DS family if you wanted to soft reset a game you could press, I think L + R + Start + Select all at once 😵‍💫

And you could even add a timeout interval if the player takes too long between presses.

It could be something modest like 4-5sec that the flairs go away.

I think I’ll test that if my next game jam game could use it.

You are so right lmaooo

BUT, it’d still be great for Keyboard controls, if it’s the keyboard alone.

If a game gets played with a keyboard, more often than not it means there’s mouse control, which is far more intuitive just bc its second nature to navigate UI with a mouse these days.

I can understand how, and I agree.

I don’t think this design got done after the wii because this works perfect for only a Wii remote.

You can comfortably press A/B with one finger each, but most games now use a gamepad layout.

Asking players to press A/B or X/O with just one finger is awkward.

Bummer. enjoy!

I’m going tomorrow, will you be there as well?

You can find DreamScape's Steam page here: store.steampowered.com/app/3569570/...

#gamedesign #questdesign #systemdesign #gamedeveloper #workinprogress #steam #systemsengineering #gamedev #indiedev #designsky #gamesky

These new designs have yet to be tested, so I'm curious to hear from other designers who've tackled similar challenges.

What's your goal when designing quests for players?

What feedback might you provide on the work I've done so far?