• Advertisement
  • Popular Tags

  • Popular Now

  • Advertisement
  • Similar Content

    • By Marinka Brussel
      Imagine a game where the characters are not defined by body regions, but rather, each body region consists of thousands of components, which would kind of replicate the real world where we consist of molecules, atoms - that would open up many, many new possibilities for creative gameplay. Can this be done on any scale with today's technology, or would the games simply require too powerful of a computer to even be playable? Are there any theoretical limits to this? Thanks
    • By Dijsktras
      Hi all,
      Does anyone here know if coloring book games are popular among little kids?
      If yes, I have the following questions:
      Do kids tend to color the same image over and over again? UI is supposed to be 'childish and crowded' or 'flat and peaceful'? Does 'kid songs' matter as in-game music? (In my current project, we have found that the audio is ignored by the adults) Anything you would like to add and I should consider?  
    • By Pasha Gubin
      Hey guys, wanna introduce to you my new arcade game!
      I'll be very grateful if you leave your impressions and recommendations in the reviews. Please, don't judge strictly, my first experience. Have a nice day!)
      Google Play: https://play.google.com/store/apps/details?id=com.ReikoApps.LeapGameSpeedEvol
    • By Eios
        I have coded small games and put some of the features from them into a platform game. But I know my art is not appealing and I don't want to plan the story and cut scenes out. That is why I am posting on the collaboration forum to see if anyone wants to make a game out of this.
      Only hobbyists apply. Please don't change your mind about it being a hobby. PM me when making your application.
      My platform game includes:
      Camera and Movement
      Moveable camera and not binded to player when pressing middle mouse button.
      Bug free jump.
      Player direction following mouse cursor.
      Good collisions.
      Platforms and diagonal slopes.
      Stored Statistics
      Level up with statistics.
      Health bars.
      Save system with continue room.
      Basic attack.
      Self heal.
      Attack and pull enemies back.
      Attack and throw enemies in the air.
      Essential Rooms
      Zoning to a new room.
      Menu with sounds.
      Game over room.
      Randomized rooms.
      Text Dialogue
      Interacting with NPC displays a message.
      Ending conversation with a key press.
      Text typing itself.
      Fast forwarding text with a key hold.
      P.S. I know everyone suffers from jealousy if someone starts selling the game and forget about the other people that worked on it. That is why we need to make sure that we use Discord. But I do not plan to sell the game.
    • By Exoaria
      I've been thinking a lot about how I want to approach the design for interactive objects in my 2D Platformer. I wanted to do something lightweight and centralised so I started work on an Event Class that embodied anything that would be interacted with. The type of interaction would be defined in the Unity Editor though a Custom GUI that I am working on.

      As you can see, this "event" would be for a moving platform. If "Is Triggered" is ticked, the Platform moves only when the player jumps onto it and activates it. Otherwise it will interpolate between the definable "Start Position" and "End Position". Depending on which "Event" (enum) is selected, the Editor properties will change and so will the behaviour of the Game Object with the event attached to it. For example, selecting "Item Collect" would mean that the Game Object is no longer a platform - no longer an object that moves when activated - it would be a stationary sprite that, when activated, would disappear and add itself into the player Inventory.
      Here's some code to show where I'm at with it:
      /* * ############################# * ##@@## INITIALIZATION ##@@## * ############################# * */ private void Awake() { SetupEvent(eventType); } public void Activate(bool calledFromTrigger = false) { if (autoTrigger && !calledFromTrigger) return; Debug.Log("Activated " + name + "!"); StartEvent(eventType); } private void StartEvent(EventType type) { switch (type) { case EventType.Movement: MovePlatform(); break; case EventType.Dialogue: break; case EventType.NPC: break; case EventType.ItemCollect: break; case EventType.Cutscene: break; case EventType.Switch: break; case EventType.Custom: break; } Don't be deceived by the snippet - this is all quite functional as of right now, but I can't help but feel I am making a mistake.
      I keep having this gut wrenching feeling pulling me to scrap it and rewrite the "Event" class to be a base class of "Interactible" and for each type, or what is currently an enum, to be a child of Interactible.
      Essentially, I am not sure whether to base my events off of one Event class, with functionality dependent on the selected "Event Type" enum... Or have the "Event Types" span multiple classes inheriting from a base "Interactible" class. I like to be able to just drag and drop, select what I want all in one place - but I feel that this is entirely impractical due to its low level of abstraction and code being all in one spot.
      Can I get some opinions? I am a relatively beginner programmer but I know code decent enough to be able to use more advanced techniques I think. Here is a screenshot of my game for context.

  • Advertisement
  • Advertisement

Some thoughts about preferences in game design

Recommended Posts

Every single person reacts to the game in a different way and even quite similar in tastes gamers can like or dislike your game design. On the GameCrafts conference in Kiev was an interesting speech about human's personality influence on the preferences and derision in games.


What is is your opinion about it and does it really meter on the prototype stage of the game design?

Share this post

Link to post
Share on other sites

For prototyping, that seems exactly right time to explore it.

Prototyping is a time to experiment with ideas and do things wrong, or do things somewhat well, so you can identify what works, what doesn't, and what works somewhat but needs improvement.

I think in the talk they're in the right direction of discussing how many different play styles can affect things for some games. If it fits the game genre, and if you have development time/budget, then go for it. People are different, and if it makes sense in your game to adapt for that, then do it. Otherwise, don't.

Share this post

Link to post
Share on other sites

When prototyping, you begin to build a foundation for your game.  When building a foundation, it's important to have a single focused vision on what your game should be.  frob is right, you should be experimental to see what works, but at the end of the day, you should know who you're making your game for, and the archetypes mentioned in this talk is an excellent start.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Advertisement