COZZER'S PROFILE

Wrong topic. :(

Well, I think both giving and receiving criticism are skills just like everything else and they can be trained and improved. °°

Personally, I find both of the reviews very good.
Sure, receiving one of them would probably make me feel bad, but it would also give me a lot of things to think about to improve myself.

And, even if a review is just "Fuck you and fuck your game", knowing there are people that hate the game so much is useful information. Sure, it's not good criticism, but it can be somehow used.

author=Max
In case you were being even 1% serious

I wasn't (and I hope there wasn't really need to confirm it), but I didn't expect to make such a "word meaning fail". XD

author=LockeZ
Well I can think of ways to do this better, and in general I've always appreciated when it's done. Usually it goes like this:

> New Game

How familiar are you with this type of game? This will affect the tutorials you see while playing. Note you can change this setting later at any time from the options menu while playing.
> I've played this game before. (All ingame tutorials are turned off)
> I've played some other RPGs before. (Game-specific systems receive tutorials as they become relevant during the game)
> I've played some other video games, but not RPGs. (Basic RPG systems and game-specific systems receive tutorials as they become relevant during the game)
> I'm not really very familiar with video games. (Basic controls, concept of a player character, etc. are explained before the game starts, plus the above tutorials all are shown)

Yeah, that was what I was advising too.
That choice will optimize the player's playing time and, actually important, will make him feel that you, the developer, CARE about him and WANT him to have fun.

I didn't suggest putting all the tutorials at the beginning. The player tells you which kind of player he is, and you adjust his experience.

For example, let's say the player is approaching is first battle.
- If he already played this game, you don't tell him anything.
- If he's already familiar with RPGs, you just explain where your game differs from the "standard RPG".
- If he's not familiar with RPGs, you probably need to explain the concept of "turn based combat".

author=Max
You perceive an awful lot of arrogance where there isn't any

Probably "arrogance" isn't the correct term. I blame my not being a native English speaker for my small vocabulary.

Still, it's something I see a lot in both Computer Science and gamemaking; the idea that the user has some kind of "duty" towards the developer. The idea that if the users doesn't have the "skills" or "patience" needed to use your program, then it's his fault (stupid words like "noob" or "luser" fly around).

author=Max
I think no matter how broad the audience you're trying to reach is, it's probably a safe bet that you can skip the computer and videogame steps at the very least

Then you exclude from your target audience people who don't know these things.
It's not a bad thing to do, but you keep repeating you want everybody to be able to play your game...

Anyway, the HUD thing is a very good idea, since it lets the player "learn by doing", but it's not appropriate for the complex mechanics of a RPG...
Still, I support it to explain at least the basic controls.

I find the title pretty arrogant.
How can you say this is a "journey" and not just "a walk", or "a stroll"?