Sounds like you're on the right track. If.you're using nhibrinate then you should write things with it from the start. That's one of albetros' biggest drawback, we had to try to retrofit.existing systems with it.Quote:
Inventory loading/saving(which is actually item saving but meh) added. It`s just a dictionary lol. And wrote some new methods and constructors for the Item class, such as converting a GameItemDomain(just a data holder for nhibernate) to ConquerItem etc. Now working on Equipment.
EDIT:
Removed all bugs related to this, basically stuff I didn`t think about before testing. Now it works as intended.
I'd use a stored proceedure to pull all user items (invent, whs and equipment) and keep them as nhibrinate objects with helper methods to let these objects be used directly as game objects (for calculations and packets). you can then just .save() them on modification without any real hassle (note, I'd do helper methods for things like... Change id. that way all stats update and savewithout you needing to remember)
Basically take how we started.to.do things with.albetros and finish them ahaha