Відео

Is this vector art?

This is a cool trailer and makes me want to play the game, but I feel like a lot was going on. I wasn't really able to see the main action. Maybe you should zoom in a little when making trailers?

Hey! Great Video! I know this is a long shot, as the video is 3 years old, but if you could answer it would be great. Is it possible to have videos/animations instead of the images? Could you point me in the right direction? Thank you!

BR ou PT?

Zombeez Game Jam on itch is awesome for indie devs. Get involved!

Could you explain a bit how your drawing the other textures as part of the tiles ? I would love to understand the logic here 😁 I looked at stencil buffer and passes, but I don't have thoses in godot4. But I will make it somehow, that's why your logic here would be very helpfull !

Thanks forn the share. The red is for texture mapping, the blue for a shadow gradient, the green for the shadow line and the black for the outline color

This looks so cool, keep it up!

Nice video, I think I might use something like this in my game!

i will become gameDev, but my age 30 year old, how old you Vectore Game Dev? please give me motivation

awesome

like the document best, a mindmap is just a thing to help you get a better picture. at the end of the day if it's just you just proceed with what feels best for you though, glhf!

Looks awesome! Objecta firther away also tend to rotate less than objects closer to the camera, so that rotating pillar at 0:54 is a great prop :D

What ever happened to just trusting your game designer instincts? You know what to do, you don't need this complicated huge document. The value dramatically drops when your doing anything more complicating that writing down small bullet points about the mechanic your are currently working on.

so it's not recommended for top down 2D/2.5D games like Octopath Traveler right?

A documentation does not need to be a document. Especially in the creative sector, the documentation is mostly visual. If you look at web design, most mockups and wireframes are considered documentation and I had some colleagues dabble with video documentation (e.g. recorded management presentations) very effectively. The "document" needs to convey the intent and help understand "The Plan" for the project. I am personally using Obsidian with a simple checklist segmented into versions where I plan out the next 2 versions while working on the current one. Documents are often used for pitches and management informations but never in my coding or design career have I seen a good document used for a project definition. If those are used to document the project, they often are outdated very quickly and updating them takes away a lot of resources that could have been put into the actual project. I like your visual approach with Mira and I considered it before myself. It helps with segmenting parts of the game and getting a quick visual overview. Zooming in and out can also help to get a feel for the current state of the project. Sometimes we tend to overlook how far a project has come already :) Nice project and video :) Keep up the good work!

Hmm dude, you hide explaining a standard practice behind a clickbait title and use all this to just advertise your game. Leaves a bit of a bad taste. To be honest :/

amazing work , assumed you'd have a lot more subscribers

amazing work 👍

Usually what we do is simply assign a z value to each layer, and move them relatively to the camera at different speeds according to their z value. Why did it cause issues for you?

super cool

😊

I'm pretty sure that's how parallax normally works

I think you're missing the presentability of a GDD. This is navigable and usable by yourself... but a GDD is not primarily for one person. As the designer of the document and having good memory, I at most reference it once every few months, but I still made one with presentability in mind because of others reading it such as team members or a publisher so they can understand what's being made. Having everything just splayed out on a field instead of linear pages is going to make it less navigable and confusing to take in.

I've been toying with using Obsidian as a nice, hierarchical way of organising many documents into a single GDD. If you've ever followed Tynan Sylvester's methodology, I think his idea repository and ToDo lists could be implemented and shared quite efficiently with the right plugins. Best of all, it's FOSS!

Kanka is what I plan to use, after I realized that campfirewriting was too restrictive. I need a tool to organize Dialogue, NPC's, Items, Skills, Quests and so on.

Looks great, would try it but by personal preference wouldn't pay for monthly subscriptions

I think what was missing from your documentation was modularity. Others already mentioning Obsidian.md, (or any markdown editor) is perfect to make your notes more modular. That way it feels less like redoing a whole word doc and more in line with what your game development environment is like, all files and folders with separate assets. I think there is some value in keeping the 'old' notes in with the new notes. Could even silo them into an 'old' folder, but still link them in the new note. Just have a good versioning naming convention.

👍

I've been looking for gold documents alternatives. I think I'll give Miro a try and combine it with Obsidian for note taking.

cool😊

I think this is an interesting approach, keep it up! On a side note I think the music was a tiny bit to loud and/or too hectic in this video

What engine do you use?

Subbed!

Top

Thats an very clever way to handle UI animations, very versatile and looks very good

so cool😊

I ❤ it

sigma awesome cool

I would love to play your game 🎮❤

I love Atlas❤

Awesome❤

Great video. Keep it up man, I'm excited to see the game release and play it

I think its overcomplicated:/

Finally, a new card suit to use as a health bar!

Some may have said already, but tying your health to your magic system is BAD. You are saying that in order to achieve combat, you have to sacrifice health, making every encounter not only dangerous, but unfair to the player, who takes on damage from simply attacking.

When I first saw the new UI I thought you would do something like each square is 1 health point and the 4 highlighted corners represent your available skills. So if you use 1 skill/consume energy you would lose one of those corners, the center square still staying the same. This goes on clockwise until you depleted all 4 of these outer corners. Now the next time you use a skill you would take 1 damage. However every time you take damage you move to the next square where all 4 corners are filled again. In theory players who use very few skills will often experience the feeling of loss because they missed out on 2-3 corners they didn't use before taking damage, so they might start using skills more agressively. On the other hand if the players use too many skills they either need to try and dodge more enemies so they can conver their HP more aggresively into energy without a fear of running out, or they might stop using the skills all the time and try to think more about when to use them and try to preserve as much HP as possible. This is just what I personally first read from the UI and thought what would happen. This system might have flaws and might not work for your game, but I thought I might share my expetations.