Top Mud Sites Forum - View Single Post

Loriel · 11-15-2002, 06:14 PM

I think we are talking at cross purposes here, and actually agreeing :
destruct(objects) will not work (as you say, destruct takes an object or a string, not an array), whereas objects->destruct() would work (if destruct were a lfun).
I don't see why you want a different reset in your "virtual" rooms than in your "real" rooms, and the "bloat" involved would in any case be negligible - the extra code would lie in one blueprint, not in all the clones, so the only case it would exist is where you have "real" rooms loaded and no "virtual" ones. However, as you say, if you want a different reset system in your virtual rooms, or want it only in the virtual rooms, put it into your intermediate inheritable.
I wouldn't wish to force its use on anybody (nor would I wish for force anybody to use Lima or MudOS) - however, my own experience of using it is that it makes virtual rooms easy. Choose whatever suits you, and use it.

11-15-2002, 06:14 PM	#10
Loriel Member Join Date: May 2002 Posts: 49	I think we are talking at cross purposes here, and actually agreeing : destruct(objects) will not work (as you say, destruct takes an object or a string, not an array), whereas objects->destruct() would work (if destruct were a lfun). I don't see why you want a different reset in your "virtual" rooms than in your "real" rooms, and the "bloat" involved would in any case be negligible - the extra code would lie in one blueprint, not in all the clones, so the only case it would exist is where you have "real" rooms loaded and no "virtual" ones. However, as you say, if you want a different reset system in your virtual rooms, or want it only in the virtual rooms, put it into your intermediate inheritable. I wouldn't wish to force its use on anybody (nor would I wish for force anybody to use Lima or MudOS) - however, my own experience of using it is that it makes virtual rooms easy. Choose whatever suits you, and use it.