How can i make it, without using ASL, so that one object, in my case a character, will follow you, allways appear in descriptions, and basically be in the same room you are in all of the time? without creating seperate ones?

#quest.currentroom#

The best way to do it shortens the code a bit (just guessing since I haven't tryed putting it down)but isn't idea for alot of objects or a large game...
Give the object a property "following". When the player steps into the room with the object in (say an imp which keeps stealing from your inventory) set the "following" property to 1 (it *should* be 0 before). After every turn the code could test every object in the game and see if it has the following property = 1 and move it into your current room.
This stops the coder writing out x number of the same code to deal with x number of objects....

There is one problem with ALL ways to do this, and that is whenever you kill off or use (if it's usable) the object following you - if you go back to the room then it will again start to follow you.
To get around this you need to check another property on the object - or see if it's still available for interaction. I put checking a property just in case it's an object which is meant to leave you at some stage, but comes back at a later time (the imp goes off to sell your stuff, in which if you kill him you'd get money).

That should work if you can put that idea into code...

Here's a QDK made demo of a "following" object, built in about 4 minutes so excuse the lack of detail :-)

The follower here is a pet cat - which once spoken to will follow the player around, but until spoken to will not. This serves as a "how to do it" example for enabling a follower.

quote:

---

' "A 'Follower' Demo"
' Created with QDK Pro 3.12

define game <A 'Follower' Demo>
asl-version <311>
start <kitchen>
game author <DaMaDbRiT>
game version <0.01>
game copyright <� AGB 2003>
game info <Created with QDK Pro 3.12>
afterturn if property <cat; following> and not here <cat> then {
move <cat; #quest.currentroom#>
msg <Fluffy follows you into the room.>
}
end define

define synonyms
end define

define room <kitchen>
prefix <the>
look <the Kitchen - ho hum>
south <hall>
end define

define room <hall>
prefix <the>
look <The Hallway - stunning>
north <kitchen>
east <lounge>
end define

define room <lounge>
prefix <the>
look <the lounge - magnificent!>
west <hall>

define object <cat>
alt <Fluffy; pet>
look msg <a small tabby cat - 'Fluffy' is the family pet.>
speak {
msg <Your voice captures the cat's attention, and she rubs against your legs miaowing loudly.>
property <cat; following>
}
prefix <a >
gender <she>
end define

end define

define text <intro>

end define

define text <win>

end define

define text <lose>

end define

---

Cut n paste this saving it as 'follow.asl' and open it in Quest / QDK to see how it is done. This is dead simple and needs a lot of refining but ought to point you in the right direction.

If the character has to do something, you can put that in an 'afterturn' script.

quote:

---

There's another way that might work for you, and it's dead easy. Simply give the object to the player, rather than the room, and write descriptions that say it is following. A simple example can be found in the game 'Spectrum' in the quest archive, vis a vis the 'takeable cat' object.

---

That works from the 'have the object following' point of view, but Adji asked for a way to have the object showing in the room description (i.e. objects/places list).

If you put the follower in the inventory - it won't show in the room!

quote:

---

Passerby suggested:

quote:
--------------------------------------------------------------------------------

There's another way that might work for you, and it's dead easy. Simply give the object to the player, rather than the room, and write descriptions that say it is following. A simple example can be found in the game 'Spectrum' in the quest archive, vis a vis the 'takeable cat' object.

--------------------------------------------------------------------------------

That works from the 'have the object following' point of view, but Adji asked for a way to have the object showing in the room description (i.e. objects/places list).

If you put the follower in the inventory - it won't show in the room!

Al

---

It might not be completely useless though, you could add a little section in 'afterturn' that moved a second object into the room if the player has the first object. They would probably need different names, though. So you'd have to compare this with the other way of doing it, and see which is easier for exactly the things you want to do.

quote:

---

Sorry. it looked good at the time.

---

It's another approach to the problem - it doesn't QUITE do what is asked for, that's all.

quote:

---

It might not be completely useless though, you could add a little section in 'afterturn' that moved a second object into the room if the player has the first object. They would probably need different names, though. So you'd have to compare this with the other way of doing it, and see which is easier for exactly the things you want to do.

---

There are almost always plenty of ways to create the same visible effect to the player - that's what makes coding such fun! (for me anyway)

The demo code I posted was the 'obvious' way to do what's required and does do exactly what Adji asked for. Although it is presented here in ASL form it was actually done in QDK and requires no knowledge of ASL to make it work.

I can think of about five other ways to do this "off the top of my head" so to speak, and although some are rather more elegant solutions, none are as easy to do.

Al

quote:

---

The way I would do it is to give the object to the player, then write in the Game properties, Print description script: If player has "cat" then print:The cat follows you into #quest.currentroom#. I checked and it works. Hope it helps!

---

That works for describing the cat as a following the player - but it doesn't leave the cat object listed in the room objects nor is the cat mentioned if the player types "LOOK" - which it should be if it is present.

Try my example from above and you'll see what I mean. It's interesting to see how different people approach the same problem though and I hope this kind of 'discussion' of how to do things will stimulate further exchanges - it is good for everyone.