symset restrictions attribute (trunk only)
Pat Rankin wrote: > I was about to also suggest that there > be a rogue/non-rogue (with perhaps a third choice meaning "both") > attribute. That way we could keep the rogue choices from being > listed in the "symset" menu and the non-rogue choices from the > "roguesymset" menu. Players who deliberately wanted to switch > over would need to modify the attribute, possibly on a cloned set. > Or perhaps they could just explicitly set their desired choices > via NETHACKOPTIONS or .nethackrc and not use the 'O' menues--the > new attribute doesn't necessary have to block which sets get used > where, just filter menu entries to display the most applicable > candidates.
This commit is contained in:
@@ -160,6 +160,7 @@ finish
|
||||
|
||||
start: RogueIBM
|
||||
Handling: IBM
|
||||
Restrictions: rogue
|
||||
S_weapon: \x29
|
||||
S_amulet: \x2c
|
||||
S_food: \x3a
|
||||
@@ -190,6 +191,7 @@ finish
|
||||
|
||||
start: RogueEpyx
|
||||
Description: Rogue level color symbol set like Epyx Rogue
|
||||
Restrictions: rogue
|
||||
Handling: IBM
|
||||
Color: Yes
|
||||
S_weapon: \x18 # up arrow
|
||||
@@ -267,6 +269,7 @@ start: RogueEpyx
|
||||
finish
|
||||
|
||||
start: RogueWindows
|
||||
Restrictions: rogue
|
||||
Handling: IBM
|
||||
S_weapon: \x29
|
||||
S_amulet: \x2c
|
||||
|
||||
Reference in New Issue
Block a user