Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Real height... Real Mountain?

Discussion in '2D' started by AlphaGrizzlyBear, Nov 27, 2022.

  1. AlphaGrizzlyBear

    AlphaGrizzlyBear

    Joined:
    Nov 11, 2019
    Posts:
    2
    Hi there, I'm trying to make a strategy game that is 2D.

    You look at the characters at a more or less 135 degree angle. They are 8 directional.

    This means the environment (plants, houses, trees, etc) all have some element of depth as well as their essential 2D ness.

    What I'd like to do is cheat perspective. The game I'm making is based on ancient warfare, and so height, and utilizing heights to your advantage, are crucial.

    My current plan is to demonstrate that something can't be seen at a certain level (in other words, you can't see the peak of a mountain, or through dense forest) by having some sort of opacity screen.

    When sprites "walk up/down" a mountain they would grow larger/smaller according to a script I'll write.

    My only issue is how to visually display a 3D mountain at 135 degrees, with pixel art!

    I've checked out some notable 2D games (early pokemon and stardew valley) and they aren't quite right. You can't access the "back" of those tall objects.

    I guess, what do I need to do? Shading? Fancy coloring? Who should I take a gander at?
    Has someone already attempted this? Is this necessarily impossible?
     
  2. flasker

    flasker

    Joined:
    Aug 5, 2022
    Posts:
    193
    2D means 2 dimensions

    you want 3 dimensions, so your game needs to be 3D if you want that

    you can do a pixel art 3D game check octopath traveler or final fantasy tactics

    in 2D there will always be one side that you cant see, thats why its called 2d
     
  3. Kurt-Dekker

    Kurt-Dekker

    Joined:
    Mar 16, 2013
    Posts:
    38,520
    It sounds like you have this massive crazy complex construct of some game idea and yet you have done absolutely nothing to realize it, at least judging from what you write above.

    Why not start with some basic tutorials for what you contemplate? No part of it will be done "all at once" but rather by iterating repeatedly, refining what you have further and further until you are happy with it.

    Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration:

    How to do tutorials properly, two (2) simple steps to success:

    Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. That's how software engineering works. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.

    Fortunately this is the easiest part to get right: Be a robot. Don't make any mistakes.
    BE PERFECT IN EVERYTHING YOU DO HERE!!


    If you get any errors, learn how to read the error code and fix your error. Google is your friend here. Do NOT continue until you fix your error. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.

    Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.

    Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. If you want to learn, you MUST do Step 2.

    Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If there's an error, you will NEVER be the first guy to find it.