This is only my first try at the design document, and it is my idea as some may know for my project.
Please read it and post creative criticisms only.
New design documents
Thanks

A little off-topic, but providing it as a .pdf would be nice.

Hey Blade, some information:
- You pan cutscenes for the reptile house, the light house and Kings Cross. These locations have never been playable from the ancient harry potter games, thus I think you should indeed integrate them in your game

Looks like a feature-list

• cool effects
• revolutionary gameplay
  
• realistic physics

What do you want us to criticise?

@FlorianP you must have trouble reading, because i did say

So therefor that must mean that if you have no criticism to post then don't post?
I don't see how than might of confused you.

The document if so people can see what i want to include in the game, and criticise on the actual document or the ideas i have.

What you have written are some more or less ordered thoughts. That's nothing to do with a design document. A design document is a detailed description of the game mechanics, locations and quests. You mentioned some locations but thats all. "There are mini games" is too less for a game mechanics description. Overall the document is much too abstract and looks more like an advertising brochure than a specification.

I doubt then you that you read anything after the bit that says there are mini games, that provides some details about the mini-quests and games that there will be in the first chapter of the game. It seems people on this forum are having trouble reading.

It seems people on this forum are having trouble accepting positively meant criticism. I read through your whole document in order to help you with feedback. There is not a single description of one of those minigames. A design document is a specification, that describes your gameplay in detail. The general remark of the existence of these games is not sufficient, even if you name the benefits of winning them. You need to describe the baseic interface of the game and how the user or player is expected to interact with the game system in detail. I'll give you an example:

Minigame Nr. 1 is called xyz. This minigame is being started whenever the player does xyz. The game starts with xyz. A screen is shown with a grid on it. There are four types of symbols on the grid. The symbols are as follows: 1. a 2. b 3. c 4. d In order to win the game the player is expected to do this and that with the symbols. He wins the game when condition xyz is reached. Incase xyz happens the game is lost. The player is then punished with xyz.

It's that much of detail that is expected of a design document. For all minigames occuring and much more important even for the main game.

If you read through it you would see that the mini-games are referenced and described, the reason every single detail of them is not written down is because:
One, it is due to change depending on coding restraints and time,
Two, as you would know if you read it that the document is the first draft, i never once said it was completed.
Yes i was looking for creative criticism, but that is more than what you wrote which in basic said "This is not a design document, it is just ideas."
Although if you think about it that is what a design document is , it is ideas which you want to make into a game.
Also the mini-games are detailed enough to get a drift of what they are, for example the lessons are mini-games. Also there will be things like quidditch, which i will not write a detailed description about as the game is a fan game and intended for fans, therefore they will know what qudditch is.

That's the second time you impute having not read the document to me. I think this is rather unkind. Especially when peoplae actually do read through YOUR stuff in order to provide YOU feedback.


Software and Software Specification are always subject to heavy changes. But "the specification could change so I'd rather not write it at all" is a rather bad argument.


You're never once said it was incomplete. But then if you say that your document could be part of a specification, well then great job. This could really be part of design document.


Fans won't read through your document. The will most probably play your game. Btw. it is a common mistake to not write things down as you think everybody know what xyz is. The goal of a design document is to specify the games content in detail to avoid misunderstandings and the document should be understandable by all types of people.