Thread: error C2061: syntax error : identifier

Your include hiearchy is way wrong, and I suggest you fix it before doing anything else.
Any header that depends on another should include that header.
For example, Player.h should include Weapon.h.
Never rely on a .cpp file including the appropriate headers that a header needs!

After that, I think you need to stop being so extreme on pointers. Remove them and try optimizing if you see a performance hit.
And don't use char for strings, use std::string instead. Your current method is unsafe.
And my last suggestion is to make the classes do actions instead, like Attack, Defend instead of TakeDamage.

Ah yes, you may also want to learn about references.

Thanks for the reply.

Yeah I know that my include hierarchy is way off, that is my problem.
I would very much like to know how I should do it instead, and how to fix my problem.

As I said before, this is my first project and I'm not really looking for the best method to do everything. I can't go from knowing nothing to knowing the best optimal way to do everything in 8~ hours. This project is only for learning, and I will keep adding/removing stuff until I realize that everything is ****ed up and I have to create a new project ... that's my way of learning.

Back to the subject at hand; I know adding weapon.h and armor.h to player doesn't solve anything. Actually I knew that they had to be there. I must've tried something different yesterday evening and therefore removing them.

What about Inheritence ? If class WEAPON, inherits from ITEM, does weapon have to know about item somehow? Like with #include "Item.h" or class Item; ?
Theese are the things I don't understand, 'who' need 'what' and 'why'.

About the string thing, I will try to change that. Actually I looked at a source code for a textbase rpg and he had done it that way (with the char[20] names and char pointers).

Thanks // Mattias

You should change to the right include hierarchy first, even if it doesn't solve the problem, because you will want this in the end, and if you make fixes before you change to the new hierarchy, you will just have to change it later and potentially break the code.

Code:

class Item;

This is called a forward declaration. It can be used ONLY if you use the type in conjunction with pointers and references, ie:
Item*
or
Item&
Any other case, you MUST include the header so the compiler can see the class definition (yes, this includes inheritance).

I don't expect you or anyone else to become a pro overnight, of course, but slowly making suggestions and changes makes everyone learn.