You can make an object inaccessible (= hidden in ASL) or invisible wherever it is. If you want the corpse to rot away, you could just use one "corpse" object and set its alias to "corpse of (whoever)".

You can't have two objects of the same name in Quest. You could give them different names and the same alias, however, so perhaps each time the player dies you could create a different corpse object - corpse1, corpse2, corpse3 etc., and then give them the required alias.

Erm, I'm just thinking in a "multi-player" type of situation here (cos that's the first thing that came to mind).

Why not have an object named "corpse" and 'clone' it, move it to the players current room, alias it as "Corpse (#playername#)", give it all your items (have it as a container perhaps? - Al have you begun a QNet lib?) then move the player away. A timer would be needed to have the "rotting" I would assume, and would need to check *ALL* the rooms in the game for corpses... Unless you can 'clone' and alter a timer (to add to the "to-do" list?).

For a single game - you wouldn't really need a corpse since the player would really see it. All you would have to do is remember the position of the player and items.... Unless you have him wander back to his body and re-enter it after he is dead...

Note : if anyone understands this post fully - they are either mentally insane or have some sort of illness which is affecting their thought! The same applies for this note!

quote:

---

(have it as a container perhaps? - Al have you begun a QNet lib?)

---

I confess I've hardly played with Quest nulti player at all as yet (Alex, why not call it Quest.NET and see if it offends Microsoft!) because I've no real need for multi-player games, and I certainly don't envisage ever running a server for the purpose of offering Quest games over the net - insufficient resources / time / money for starters!

That said, I understand that the code for multi user isn't THAT different from what's needed in single user mode, so maybe I'll do something soon.

Correct me if I am wrong, but multi user games must require a completely different mindset to code, because suddenly it is a "real time" environment, a real 'someone else' is in the game world and they aren't paused while your player contemplates his next/best move, this is completely different to the turn based stop-go action of most regular Adventure Games.

Don't multi-player games mostly turn into a "he who gets there first wins" treasure hunt - or a "he who has the best weapon wins" virtual bloodbath?

Al

quote:

---

Just to answer CW's question: The corpses are for sacrificial purposes--you can sacrifice them and recieve a health bonus from the Gods.

---

quote:

---

(Alex, why not call it Quest.NET and see if it offends Microsoft!)

---

quote:

---

Correct me if I am wrong, but multi user games must require a completely different mindset to code, because suddenly it is a "real time" environment, a real 'someone else' is in the game world and they aren't paused while your player contemplates his next/best move, this is completely different to the turn based stop-go action of most regular Adventure Games.

---

quote:

---

Don't multi-player games mostly turn into a "he who gets there first wins" treasure hunt - or a "he who has the best weapon wins" virtual bloodbath?

---

Maybe a system where one player does something with a certain ammount of points? When the points are out then it's the other players turn... That sound good...