Talk:Public Builder's Guide
From Tapestries MUCK
JadeWizard (Talk | contribs) m (rules-lock property suggestion) |
JadeWizard (Talk | contribs) m (clarification) |
||
| Line 1: | Line 1: | ||
| - | '''Suggestion:''' I think we should add a note here that the rules-lock property should include or incorporate the name of the establishment, or in some other way be made unique. At the time of writing, "Dragon's Hotspring Inn and Brothel" rules-lock property is "_RulesRead?:yes". If we do not make a rule that the property incorporates the name of the establishment (e.g. _BrothelRulesRead?:yes, or _DHIIRulesRead?:yes, or whatever) or is made in some other way unique, it could be that people setting rules-lock properties for one place will, by accident, receive a free pass to another place using the same property string. The chances of this may seem low right now but if we want to "guarantee" that the property reliably indicates an agreement to the rules, a unique rules-lock property is a good idea. [[User:JadeWizard|JadeWizard]] 18:49, 30 March 2007 (PDT) | + | '''Suggestion:''' I think we should add a note here that the rules-lock property should include or incorporate the name of the establishment, or in some other way be made unique. At the time of writing, "Dragon's Hotspring Inn and Brothel" rules-lock property is close to "_RulesRead?:yes". I will not say what the property actually is, because one should technically be required to read the rules in order to learn it, but it is generic as I have shown here. If we do not make a rule that the property incorporates the name of the establishment (e.g. _BrothelRulesRead?:yes, or _DHIIRulesRead?:yes, or whatever) or is made in some other way unique, it could be that people setting rules-lock properties for one place will, by accident, receive a free pass to another place using the same property string. The chances of this may seem low right now but if we want to "guarantee" that the property reliably indicates an agreement to the rules, a unique rules-lock property is a good idea. [[User:JadeWizard|JadeWizard]] 18:49, 30 March 2007 (PDT) |
Revision as of 01:53, 31 March 2007
Suggestion: I think we should add a note here that the rules-lock property should include or incorporate the name of the establishment, or in some other way be made unique. At the time of writing, "Dragon's Hotspring Inn and Brothel" rules-lock property is close to "_RulesRead?:yes". I will not say what the property actually is, because one should technically be required to read the rules in order to learn it, but it is generic as I have shown here. If we do not make a rule that the property incorporates the name of the establishment (e.g. _BrothelRulesRead?:yes, or _DHIIRulesRead?:yes, or whatever) or is made in some other way unique, it could be that people setting rules-lock properties for one place will, by accident, receive a free pass to another place using the same property string. The chances of this may seem low right now but if we want to "guarantee" that the property reliably indicates an agreement to the rules, a unique rules-lock property is a good idea. JadeWizard 18:49, 30 March 2007 (PDT)
