Sessions vs. Database for short-lived data

[Sinzygy]

Which one is better for storing fast-living data? Sessions or a database?

Example: picture KoL and their battle system: You hit once, the monster hits once. Then you get to chose again what you want to do (attack again, use item, flee).
Now, which one is a better way to store the monster you're currently fighting and it's current hp?

[Zeggy]

Well, sessions are not as secure as databases, so they could be manipulated for cheating in the game.
I would say, go for databases

That way you could also resume battles if a player leaves and comes back the next day.

[Sinzygy]

Yeah, those were my thoughts as well.

well, I guess I'll go with the database-way then.

[beam]

Yeah, definitely stored in database. That way, if a player accidentally closed the browser window or something, they could pick up the battle where it left off.

[Sinzygy]

heh, I just had a nice idea:

I'ma go store the data of the monster in a seperate table and make it so that every player (or the players from the same guild) can attack it simultaniously.
This way there will be some slight Co-op fell... or at least that's what I hope it will accomplish

[Zeggy]

Eh? How would that work?
I had a similar idea, but only for boss monsters that would actually require many players to attempt to kill it, and there would be a limited amount of those monsters.

[Sinzygy]

I would store the unit  and the battle-location in a seperate table.
this table would also include fields for when the monster was first attacked, by which player and by which guild.
Now every player of tht guild that visits the same location get's a to chose to either find and attack a new monster or attack an already found monster.
But the monster will only be fightable 5 minutes (or so) from the last attack. So the guild would have to work together and plan it accordingly to actually kill it.
And when the monster is killed everyone that fought it will gain some xp, in relation of how often he fought the monster. (So a player that attacks 3 times and a player that only attacks once will get 3/4 and 1/4 of the total experience)

And yes, this will probably only be done for boss monsters, quest related monster or really, really strong monster.

[Shapulin]

but thats is easy if you design the database with inheritance.... and create a instance of the moster type in relation with the player and the time of creation for each battle....

so the instance is not longer living i they time creation is more than X or if they last attack time is more than X or something like that