TinTin++ Mud Client The TinTin++ message board

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
TinTin++ Mud Client

How to deal with blocking doors/monsters?

 
Post new topic   Reply to topic    The TinTin++ message board Forum Index -> General Discussion
View previous topic :: View next topic  
Author Message
Agaton



Joined: 20 Oct 2012
Posts: 3

PostPosted: Tue Oct 23, 2012 6:01 pm    Post subject: How to deal with blocking doors/monsters? Reply with quote

Hi!

My mapping is going well. Cool

I'm just wondering how everyone out there tackles locked doors and monsters blocking your way so the mapper doesn't walk through it?
Back to top
View user's profile Send private message
Slysven



Joined: 10 Apr 2011
Posts: 365
Location: As "Jomin al'Bara" in WoTMUD or Wiltshire, UK

PostPosted: Tue Oct 23, 2012 8:52 pm    Post subject: Reply with quote

Well there is the room flag AVOID that you can set (#map {roomflag} {avoid} {on}) in the room concerned (use #map {goto} {<vnum>} to get there if you don't want to return there in your MUD) which should prevent the route finding mechanisms from using that room.

If the desire is not so strong to stay out of that room but you'd rather go around it if you possibly can, you can just assign it a high weight, default is 1.000 (so #map {set} {roomweight} {100.00} ought to do it). I think 500.00 is the limit for the system in that if that total is exceeded than such a route is no longer considered a route; otherwise if that is the only way to read the destination will it be used (for the value I just quoted in reality the mapper should prefer an alternative route of up to 99-ish extra rooms instead).

You can lock an exit from a room with #map {exitflag} {<exit>} {avoid} {on}, which IIRC also ought to stop a particular way out of a room from being used by the route finder - though I think I put in extra code in my hacked TinTin++ to either moan loudly if I tried to manually use such an exit or to enforce NOT being able to use it - but I can't recall now what the standard issue code does...

I hope that gives you some ideas as to what is possible, you can also "embed" extra stuff in an exit direction with the #map {exit} {<exit>} {command} {<extra stuff>} which could include things like {open door; e; close door} for things that work in real time in the MUD (i.e. the door opens instantly), if you have to wait for something to happen (a reply from the MUD) before you can pass you can get fancy with an #ACTION and #UNACTION in that "extra stuff" but I'd advise to also lock the exit as in the previous paragraph otherwise you will run into problems when the route finder tries to run through the exit...

I hope this gives you some ideas as to what might be possible...
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    The TinTin++ message board Forum Index -> General Discussion All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Get TinTin++ Mud Client at SourceForge.net. Fast, secure and Free Open Source software downloads Get TinTin++ Mud Client at SourceForge.net. Fast, secure and Free Open Source software downloads
TinTin++ Homepage

Powered by phpBB © 2001, 2002 phpBB Group