Client and Server side materials. about polyhedron-engine

[WatIsDeze]

Just picked a random few folks who know each their own share in the material world(what might belong in them), and about server/client -games development.

Enjoy, we're gonna do this one also.

[Admer456]

Just don't write separate classes for client and serverside materials. It's best to have a universal, generic way of accessing them.

[WatIsDeze]

Just don't write separate classes for client and serverside materials. It's best to have a universal, generic way of accessing them.

As it stands, the code resides in the vkpt folder but is really quite unrelated to it. It'd perhaps require a bit of #if CL_GAME or #if SV_GAME here and there, which you can minimize. And as a result, it'd end up in sharedgame. So was my plan :)

[Paril]

Just don't write separate classes for client and serverside materials. It's best to have a universal, generic way of accessing them.

This was my advice to him when we talked about it as well. Use a common parser that converts the on-disk representation into an in-memory one, and the various systems can pull out whatever data it needs from it. This is what we do in Quetoo with our materials as well.