Full Games List
Featured Games
New Games
Reviews
Media
Images
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Misaos
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
Locker
Play ListsSTATUS
For my final project for game development, I have to create a game and provide full documentation.
Red_Nova- 09/03/2014 02:09 PM
Posts 
Pages:
1
Red_Nova
Sir Redd of Novus: He who made Prayer of the Faithless that one time, and that was pretty dang rad! :D
9192
CloseIt's a shame I can't use Soul Sunder, or else this project would be cake.
Oh well. I'll just have to make a whole new game from scratch... This'll be exciting!
Oh well. I'll just have to make a whole new game from scratch... This'll be exciting!
Red_Nova
Sir Redd of Novus: He who made Prayer of the Faithless that one time, and that was pretty dang rad! :D
9192
author=JJJ7
Gam Mak!
Mak Gam!
Mak... Gam? Gam Mak!
author=unity
Ooooh, can I play it when it's done? :D
Everyone can play it. Part of the requirement is to have it available for download somewhere. So I'm probably gonna make a game page here and have it available for download.
author=kentona
I bet you didn't see that one coming!
I know, right?! Make a game for a game development course? That totally came out of left field!
"Your final project is to administer a web forum catering to hobbyist game developers. It is worth 35% of your grade."
Red_Nova
Sir Redd of Novus: He who made Prayer of the Faithless that one time, and that was pretty dang rad! :D
9192
Like the documentation? I hate that part. I'd rather just make the game.
... Yes, I understand it's importance in a professional environment. But I don't see the point if I'm doing this alone.
That's such an UNFAIR assignment!! I can't imagine why ANYONE would want to do that....
... Yes, I understand it's importance in a professional environment. But I don't see the point if I'm doing this alone.
author=kentona
"Your final project is to administer a web forum catering to hobbyist game developers. It is worth 35% of your grade."
That's such an UNFAIR assignment!! I can't imagine why ANYONE would want to do that....
Okay serious moment here: documentation is fucking important.
I have worked for 10 years in the IT industry and I am telling you it is critically important that you have comprehensive, well written, unambiguous, logically organized documentation for any and all projects you work on. Yes, even on solo projects. Especially on solo projects.
If you can't see the point of it, then you do not yet fully understand the importance of it in a professional environment.
I am not going to go on about why it is, either. I am just telling you fucking do it man. You'll thank me in 5 years time when you habitualize good documentation and have it save your ass numerous times.
You're welcome.
I have worked for 10 years in the IT industry and I am telling you it is critically important that you have comprehensive, well written, unambiguous, logically organized documentation for any and all projects you work on. Yes, even on solo projects. Especially on solo projects.
If you can't see the point of it, then you do not yet fully understand the importance of it in a professional environment.
I am not going to go on about why it is, either. I am just telling you fucking do it man. You'll thank me in 5 years time when you habitualize good documentation and have it save your ass numerous times.
You're welcome.
Red_Nova
Sir Redd of Novus: He who made Prayer of the Faithless that one time, and that was pretty dang rad! :D
9192
Oh yeah, I understand that documentation is important. When I worked with unity and Sooz for the IGMC, we NEEDED to keep track of all the changes we made via online documentation. So I have firsthand experience that documentation goes a loooooong way.
I just think it's much less important when you're working solo.
I just think it's much less important when you're working solo.
author=kentona
Okay serious moment here: documentation is fucking important.
I have worked for 10 years in the IT industry and I am telling you it is critically important that you have comprehensive, well written, unambiguous, logically organized documentation for any and all projects you work on. Yes, even on solo projects. Especially on solo projects.
If you can't see the point of it, then you do not yet fully understand the importance of it in a professional environment.
I am not going to go on about why it is, either. I am just telling you fucking do it man. You'll thank me in 5 years time when you habitualize good documentation and have it save your ass numerous times.
You're welcome.
Hmm... Sounds like this is something I should start doing too. :D Do you do documentation for your RPG Maker projects, too, kentona?
author=Red_Nova
I just think it's much less important when you're working solo.
I imagine it plays a larger role should you mess something up. You'll need to get older versions/codes or some place and make troubleshooting aside from the game itself. You can't always pinpoint it exactly just by looking at the game.
Also depending on the endinge and stuff ..
.. but I wouldn't know. It's always good to have some documentation of whatever you've been doing.
Red_Nova
Sir Redd of Novus: He who made Prayer of the Faithless that one time, and that was pretty dang rad! :D
9192
I would like to repeat Unity's question as well. I actually didn't see that part about documentation being important on solo projects that you wrote, Kentona.
I certainly write out notes, like what kind of weapons, items, skills, etc. for my own projects, but those are for my eyes only, and not written in a way that someone else would understand.
When I hear the word, "Documentation," I think of it like a professionally written document that is meant to be read by everyone. Is that what you're talking about in terms of documentation for solo projects?
I certainly write out notes, like what kind of weapons, items, skills, etc. for my own projects, but those are for my eyes only, and not written in a way that someone else would understand.
When I hear the word, "Documentation," I think of it like a professionally written document that is meant to be read by everyone. Is that what you're talking about in terms of documentation for solo projects?
Early on, I didn't write any kind of documentation whatsoever. I was more focused on "does it work" than "how this works". That's what I think documentation is for, though. Explaining how something works with the vague possibility of inspiring ideas for someone else to try.
Of course, there's always the more practical standpoint of looking at your own code, and trying to figure out why you did it "that way" rather than "this way" (if that makes any sense). Documentation would show that reasoning. Or, at least I believe that it should.
Of course, there's always the more practical standpoint of looking at your own code, and trying to figure out why you did it "that way" rather than "this way" (if that makes any sense). Documentation would show that reasoning. Or, at least I believe that it should.
The kinds of documentation you need differ on the project and differ depending on how many people you have, but it's almost always incredibly helpful to have.
If you're solo, documents are a great way to organize your thoughts and plans, as well as serve as a to-do list for motivation and a historical record of the progress you've made in case you need it for reference. Some things don't need documentation, but I highly recommend it even for small projects.
For team projects, documentation also serves as a way of communicating with your team - to ensure you're all cooperating and understand what the final, unified goal is. You can use them to organize who's working on what, and what still needs to get done. Big professional documents like a GDD are good for making sure everyone understands what the final goal is, although you should be careful to keep some malleability.
Anyway, I totally use documents for any project that's gonna take me more than 2 hours to finish, even if it's just something like a to-do list in a google doc.
If you're solo, documents are a great way to organize your thoughts and plans, as well as serve as a to-do list for motivation and a historical record of the progress you've made in case you need it for reference. Some things don't need documentation, but I highly recommend it even for small projects.
For team projects, documentation also serves as a way of communicating with your team - to ensure you're all cooperating and understand what the final, unified goal is. You can use them to organize who's working on what, and what still needs to get done. Big professional documents like a GDD are good for making sure everyone understands what the final goal is, although you should be careful to keep some malleability.
Anyway, I totally use documents for any project that's gonna take me more than 2 hours to finish, even if it's just something like a to-do list in a google doc.
slash summed up my thoughts pretty much exactly. I would like to add that it is also extremely helpful in troubleshooting during the development process. It also serves as a record for all of the ideas you had and the rationale for your reasons for including it/discarding it (even if it isn't explicitly written, you can usually infer your reasoning).
it is also extremely helpful when a year later you come back to it to fix up some obscure bugs, and you can figure out what you were attempting to accomplish and what generally the project was about.
Also also, I was talking in an extremely broad sense for IT projects, and not specifically game development projects.
it is also extremely helpful when a year later you come back to it to fix up some obscure bugs, and you can figure out what you were attempting to accomplish and what generally the project was about.
Also also, I was talking in an extremely broad sense for IT projects, and not specifically game development projects.
Pages:
1
