Top Mud Sites Forum - View Single Post

chaosprime · 02-02-2008, 01:41 PM

1) My understanding of the matter is that duplicating functionality is fine as long as it's clear that your product is not zMUD or CMUD, and in the course of developing your application you don't violate any licensing terms you've agreed to in order to use zMUD or CMUD. IANAL, YMMV.
2) Much like #1.
3) No idea.
4) You might want to think about an extension protocol that MUDs could use to communicate geoinformation, such differences in scale between rooms, to your tool. If a MUD knows that room A is 5x5 meters and room B is 200x100 meters, it may turn up helpful if it can tell your application this in a standardized way. The same might go for terrain types, levels of exposure to weather, interactive service offerings like shops and taverns, and so on. If you design a protocol like that and do it well, you could wind up making a contribution that goes significantly beyond your particular application.

02-02-2008, 01:41 PM	#2
chaosprime Member Join Date: Jul 2007 Home MUD: Lost Souls Posts: 199	Re: Mapping tool 1) My understanding of the matter is that duplicating functionality is fine as long as it's clear that your product is not zMUD or CMUD, and in the course of developing your application you don't violate any licensing terms you've agreed to in order to use zMUD or CMUD. IANAL, YMMV. 2) Much like #1. 3) No idea. 4) You might want to think about an extension protocol that MUDs could use to communicate geoinformation, such differences in scale between rooms, to your tool. If a MUD knows that room A is 5x5 meters and room B is 200x100 meters, it may turn up helpful if it can tell your application this in a standardized way. The same might go for terrain types, levels of exposure to weather, interactive service offerings like shops and taverns, and so on. If you design a protocol like that and do it well, you could wind up making a contribution that goes significantly beyond your particular application.