Let's suppose you want to *really* swallow that fur and trap them inside yourself. How can you go about this? It's rather easy to make a stomach or whatever-space to stuff them in. There's a variety of ways so but I'll keep it simple.
@dig Belly
Note the database number it generates (in this example it will be #12345). Now we have a belly but no way to get there without a teleport.
@create Coin
It can be anything as we can @name it to something else later... Now for the exit into our belly...
@action Morphygulp=coin
@link Morphygulp=#12345
And to let everyone know what's happening...
@succ Morphygulp=Morphy stuffs you in and *gulps* you down whole!
@osucc Morphygulp=is grabbed by Morphy and with a huge *gulp*, stuffs
%o down whole!
@odrop Morphygulp=suddenly slides in from above...
That's it! You're done. And it didn't require any MPI at all. You should go back and @desc everything though, especially your belly at the very least. Another suggestion is adding an exit back out of the belly which leads back to you. First go into the bellyroom and then...
@action out=here
@link out=me
And that should make an exit leading to wherever you are. Of course
you can't use it, that would be a paradox. You might want to set
the exit's succ/osucc/odrop too so when the fur escapes from inside you'll
know it.
The problem with swallowing a fur is once they end up inside, you can't hear them anymore! (Yes, you can page them but that's no fun) With a handy MUF program you can hear them struggle in their new home and if you're adventerous, even let them hear what's going on outside too... First you should teleport into your belly room with...
@set here=_listen:#133065 (This number must not change)
@set here=listen/dest:178526 (Your number goes here)
@set here=listen/filter:off
@set here=listen/power/on
@set here=listen/pre:|Inside you| (This is what you see
when the prey makes noise inside)
This is all fine and if you want to keep tabs on your prey but what if they want to hear you gloating over your newly swollen belly? Since this listen.MUF program only transmits in one direction, we have to set up another set of settings pointing into the belly. Remember that coin object we made with the way into your belly? Go get it. The coin will be the audio pickup for the prey inside your belly...
@set coin=_listen:#133065 (This number must not change)
@set coin=listen/dest:12345 (The belly room's number goes here)
@set coin=listen/filter:off
@set coin=listen/power/on
@set coin=listen/pre:|Through the muffling walls| (This is what
they see when there's noise made)
Now let's say you went out and swallowed a fur. Suppose you would like it if they could still see out like being able to see what a nice bulge they make in your tummy? No problem. With this bit of coding, they can see not only you but other things in the room too. Neaters! The useage is lookout object and you don't have to use the word lookat if you don't want to.
Using the numbers above lets get to it... the easiest way to do this is to get into your own belly room. @tel #12345 first...
@action Lookout=here (We want to attach the action to the belly
room)
@link Lookout=#82576 (This number must be used, it links to
the Sensor.MUF program)
@set Lookout=goto:178526 (Your DB number goes here...)
@set here=/_map/ref:178526 (...and here)
Now to test this you'll have to swallow a fur or zombie/puppet and ask
them to try it out by doing something like lookat out.
Once you've had you meal (I hope the prey was delicious!) you might be feeling a little proud of what you've done and want to show this to the world... or at least the other envious predators and waiting prey. Assuming you used a MPI description you can insert the following into your information so that when you've fed, it shows.
Using #12345 as the bellyroom I'll show you a real basic template you can copy. You can edit the underlined text to suit your own description better.
{if:{contents:#12345}, Rubbing his tummy{lit:,} it bulges out with a recent meal consisting of {commas:{contents:#12345},\, and ,v,{name:{&v}}}!}
Note the {lit:,} to prevent the {if} from thinking the comma is a the seperator between TRUE and FALSE statments. Actually, the text won't even show if there's nothing in room #12345. But let's suppose we do want something to let furs know he's got a empty stomach.
{if:{contents:#12345}, Rubbing his tummy{lit:,} it bulges out with a recent meal consisting of {commas:{contents:#12345},\, and ,v,{name:{&v}}}!, He rubs his tummy as it grumbles faintly{lit:,} gazing to you rather hungrily.}
Now the FALSE statement will be inserted in his description when he's got an empty stomach. How is that done you ask? Ok, like this for example...
As you look him over, from flicking triangular ears to his padded
feet, Liono seems cheerful enough and glances back with his blue eyes.{if:{contents:#12345},
Rubbing his tummy{lit:,} it bulges out with a recent meal consisting of
{commas:{contents:#12345},\, and ,v,{name:{&v}}}!, He rubs his tummy
as it grumbles faintly{lit:,} gazing to you rather hungrily...}
Now the basic intenal room will work on Tapestries but there's also another method that's valid and requires no action on the prey's part (good for non-consentual vore scenes). First, as with the basic setup, you'll need to @dig a room but the object is optional and you don't have to drop it. If you make the container object then use it's name and not "me". And remember that you can only assign ONE container room for each container object. What that means is you can only have one internal room assigned to you. If you want more you'll have to make an container object for each additional internal room.
@set me=_container?:yes
@set me=_silent?:yes
@set me=_inside/room:12345 (The number of the internal room
will go here)
This next section is optional but spices up the container and the messages you'll display when you use the container.
@set me=put:opens grabs %n and swallows %o whole!
@set me=pull:makes a magical incantaion and restores %n as if nothing
happened...
Now this line will display the @desc as normal and then list the contents, if any, to you the owner of the container object. If you used the MPI description for the container object (like yourself) then I'd avoid doing this as I don't know if @1041 will execute the MPI.
@desc object=@1041 It's a generic container object, oh boy!
And settings for they prey or any object you plan on putting inside a container including yourself. If you, the prey, decide you don't want someone to suddenly grab you in the middle of a conversation then just make that yes below a no.
@set prey=J
@set prey=_putme_ok?:yes
The put/pull useage is rather straightforward...
put <object> in <container>
put <object>=<container>
pull <object> from <container>
pull <object>=<container>
One more note: This is for Tapestries. The put/pull on FurryMuck is a bit different in that it requires you make an @action for the command put/pull.
I hope this helps and please feel free to experiment. You can always @recycle the mess and start over.