Even if it's only a single page it's often worthwhile to at least make a checklist of needed assets (code, art, sound), and a short overview of of the general idea behind the thing. It keeps the scope of a project in perspective, and provides a clear and objective measure of progress. It also gives you something to be accountable to, which is important if you work a day-job and develop on the side. Plus you engage a different part of your brain when you have to write everything down, and it's entirely possible that part of your brain will notice things about your game concept that were not apparent with it all just sloshing around in your head.
Any of them would work. What data you need to store and how you store it are independent from each other. Figure out what values you need to save, create a save object to store those values, convert that object into a JSON string and save to PlayerPrefs or a File.
I recently began a new game project that is much bigger in scope than any of my earlier projects. I decided it was time to build structure for myself, as I didn't want to lose my thoughts in my head. I did some online research and then took about an hour to write up a template. I then filled out my template in a few more hours and soon got to work on my project. I have found that with more structure I can work much more efficiently and I feel much better about my progress as I'm reaching milestones that I've set for myself, which really boosts my confidence and interest in my game. The template is only 2 pages long, and when filled, it became 7 for me. The template is a simple 8-point detailing of the game, and takes a few hours to fill out. It's very well organized and uses proper header notation so that you can add a table of contents if you wish. If you're looking for something along these lines, I recommend checking it out: docs.google.com/document/d/1VfmNnSW3egCWIKkgykUOEoxFh1Pg5HElyUnqMUDakW8/edit?usp=sharing
I would suggest to make a game design document only after an initial prototyping phase. Getting the core systems nailed down and fun (dev environment) and only then assembling a detailed list of production tasks. Of course, a game with a proven core game loop (episode / follow up project / ripoff) is much easier to nail down early, and write a document for.
I have very been taking this agile approach. However without fully detailing everything I’m going to do, I’m struggling “budgeting” the project. I have been taking each “milestone” at a time to work out what I need, however I am being approached by publishers asking to budget the whole projects Any advice on doing this?
I think 2 days ago i read the GDD of Race'n Chase (ancestor of GTA). It was written very clear. I think it was 10 pages. I think it all about what type person is you. me? I feel confortable making somtehing that has a roadmap.
How much do you design before you start a prototype? How detailed are your designs?
Im starting out so i guess i need to note everything that goes thro my head haha
Even if it's only a single page it's often worthwhile to at least make a checklist of needed assets (code, art, sound), and a short overview of of the general idea behind the thing. It keeps the scope of a project in perspective, and provides a clear and objective measure of progress. It also gives you something to be accountable to, which is important if you work a day-job and develop on the side. Plus you engage a different part of your brain when you have to write everything down, and it's entirely possible that part of your brain will notice things about your game concept that were not apparent with it all just sloshing around in your head.
pls pls pls help me i want to make a sandbox game but i need a save/load system
pls how to make it >3
Check out my videos on several methods of Saving and Loading
th-cam.com/play/PLzDRvYVwl53vRrMuPBkNNZUmnl1jCHcHs.html
Any of them would work. What data you need to store and how you store it are independent from each other.
Figure out what values you need to save, create a save object to store those values, convert that object into a JSON string and save to PlayerPrefs or a File.
I recently began a new game project that is much bigger in scope than any of my earlier projects. I decided it was time to build structure for myself, as I didn't want to lose my thoughts in my head. I did some online research and then took about an hour to write up a template. I then filled out my template in a few more hours and soon got to work on my project. I have found that with more structure I can work much more efficiently and I feel much better about my progress as I'm reaching milestones that I've set for myself, which really boosts my confidence and interest in my game.
The template is only 2 pages long, and when filled, it became 7 for me. The template is a simple 8-point detailing of the game, and takes a few hours to fill out. It's very well organized and uses proper header notation so that you can add a table of contents if you wish. If you're looking for something along these lines, I recommend checking it out: docs.google.com/document/d/1VfmNnSW3egCWIKkgykUOEoxFh1Pg5HElyUnqMUDakW8/edit?usp=sharing
Thanks man, i was looking for something like this ^^
Really cool man, thanks for sharing :)
Dude how did you knew i have to make a GDD right now!? Lol this video is just what i needed, thanks :D
as a solo designer iv had no troubles keeping the ideas in my head and changing them as i go.
Yeah I get you. I usually write down the basics, but the minor stuff I keep in my head too.
Not something I had considered before! Thanks!
Awesome video, dude!
Thanks!
I read the title like "God, is it worth it?".
Yes
Perfect video! One of the most helpful videos I've ever watched.
Glad to hear it!
I would suggest to make a game design document only after an initial prototyping phase. Getting the core systems nailed down and fun (dev environment) and only then assembling a detailed list of production tasks.
Of course, a game with a proven core game loop (episode / follow up project / ripoff) is much easier to nail down early, and write a document for.
Great video!
Great info, thanks, man.
Oh man finally I found what I need ? 😍😍😍
I usually just make a few notes in a notepad.
However, I would definitely make a serious document when working with other people.
Great work
!!!عرب؟؟
@@rockerxplayz3201
how did you fraking read it
@@rockerxplayz3201
then tell me hello i am smart with arabic language
@@rockerxplayz3201
ok
i wil tell u what i mean by arab
we use it to ask if someone is Arabic
Oh thanks
What is a design phase of an fps game?
This is such a great video. :D
it depends on your own game if its big i think you should need it but if your game is small i don't think you need it
I have very been taking this agile approach. However without fully detailing everything I’m going to do, I’m struggling “budgeting” the project. I have been taking each “milestone” at a time to work out what I need, however I am being approached by publishers asking to budget the whole projects
Any advice on doing this?
I do GDD if I'm planning on making a commercial product
I say you should do it if you are serious about the project.
A bit distracting B role, but nice video overall
game at 3:12? thanks
It's one of the Anno games, can't remember exactly which one
I think 2 days ago i read the GDD of Race'n Chase (ancestor of GTA). It was written very clear. I think it was 10 pages. I think it all about what type person is you. me? I feel confortable making somtehing that has a roadmap.
thank you
When r u able to do a cops and robbers theme game and do a tutorial on it?
Hi
the audio visual animation is pretty distractive and unnecessary. i would recommend to stop doing that.
Don't watch, just listen?