![]() |
![]() ![]() ![]() ![]() ![]()
|
Author | Topic: Suggestion for next version.. |
Tanin |
![]() For the next version of Quest I'd recommend the following.. When setting a room's exits, it would save alot of time if - when you set room A's exit to B, room B's corresponding exit is automatically linked to room A. I've played around with mud codebased like Smaug, and the Smaug editor does this for you and it saves ALOT of time. I just got done building a yard and it took me nearly two hours. Also occasionally there seems to be an error when saving the game (see other post) it's easy to get around this error but it is still a hassle. |
Tanin |
![]() One more thing.. This automatic linking of rooms would also cut down on errors in a rooms exit. i.e. room A should exit to B but instead it exits to C due to programmers error. Food for thought. |
DarkAng3l |
![]() Yes, but the programmer may not want it to happen. Lets say you enter room B and the door locks behind you. But indeed, it could save some time. DarkAng3l |
Computer Whizz |
![]() This is easily fixed in two ways: Message box pops up asking whether to link to room ("Do you wish to automatically set the exit in this room?"). Or a setting in the options to have automatic linking "On/Off". Possibly both (a tick box in the message box, of "Don't show this again?"). Computer Whizz |
Alex |
![]() It's something that's on the "to do" list, but it wouldn't be compulsory - there will be an option allowing you to get QDK to automatically add the "other" exit, but you'll be able to override this by ticking a "one-way" checkbox. |
Tanin |
![]() It was just a suggestion - you all have good points. However, in most circumstances, it would save time. A tick box that says "Auto link to corresponding room" would work. |