Fixed headers on contribs, they were still referring to the old base*.py -style files under gamesrc.
This commit is contained in:
parent
ad63abee39
commit
ca32950d90
4 changed files with 159 additions and 147 deletions
|
|
@ -14,12 +14,17 @@ while puppeting a Character already before.
|
||||||
|
|
||||||
Installation:
|
Installation:
|
||||||
|
|
||||||
Import this module in game.gamesrc.basecmdset and
|
Read the instructions in game/gamesrc/commands/examples/cmdset.py in
|
||||||
add the following line to the end of OOCCmdSet's at_cmdset_creation():
|
order to create a new default cmdset module for Evennia to use (copy
|
||||||
|
the template up one level, and change the settings file's relevant
|
||||||
|
variables to point to the cmdsets inside). If you already have such
|
||||||
|
a module you should of course use that.
|
||||||
|
|
||||||
|
Next import this module in your custom cmdset module and add the
|
||||||
|
following line to the end of OOCCmdSet's at_cmdset_creation():
|
||||||
|
|
||||||
self.add(chargen.OOCCmdSetCharGen)
|
self.add(chargen.OOCCmdSetCharGen)
|
||||||
|
|
||||||
|
|
||||||
"""
|
"""
|
||||||
|
|
||||||
from django.conf import settings
|
from django.conf import settings
|
||||||
|
|
@ -182,4 +187,3 @@ class OOCCmdSetCharGen(default_cmds.OOCCmdSet):
|
||||||
#super(OOCCmdSetCharGen, self).at_cmdset_creation()
|
#super(OOCCmdSetCharGen, self).at_cmdset_creation()
|
||||||
self.add(CmdOOCLook())
|
self.add(CmdOOCLook())
|
||||||
self.add(CmdOOCCharacterCreate())
|
self.add(CmdOOCCharacterCreate())
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -21,7 +21,9 @@ That's it. The cmdset in this module will now be used instead of the
|
||||||
default one.
|
default one.
|
||||||
|
|
||||||
The initial login "graphic" is taken from strings in the module given
|
The initial login "graphic" is taken from strings in the module given
|
||||||
by settings.CONNECTION_SCREEN_MODULE. You will want to edit the string
|
by settings.CONNECTION_SCREEN_MODULE. You will want to copy the
|
||||||
|
template file in game/gamesrc/conf/examples up one level and re-point
|
||||||
|
the settings file to this custom module. you can then edit the string
|
||||||
in that module (at least comment out the default string that mentions
|
in that module (at least comment out the default string that mentions
|
||||||
commands that are not available) and add something more suitable for
|
commands that are not available) and add something more suitable for
|
||||||
the initial splash screen.
|
the initial splash screen.
|
||||||
|
|
|
||||||
|
|
@ -18,9 +18,13 @@ There is also a simple Yes/No function supplied. This will create a
|
||||||
one-off Yes/No question and executes a given code depending on which
|
one-off Yes/No question and executes a given code depending on which
|
||||||
choice was made.
|
choice was made.
|
||||||
|
|
||||||
To test, import and add the CmdTestMenu command to the end of the default cmdset in
|
To test, make sure to follow the instructions in
|
||||||
game.gamesrc.commands.basecmdset. The test command is also a good
|
game/gamesrc/commands/examples/cmdset.py (copy the template up one level
|
||||||
example of how to use this module in code.
|
and change settings to point to the relevant cmdsets within). If you
|
||||||
|
already have such a module, you can of course use that. Next you
|
||||||
|
import and add the CmdTestMenu command to the end of the default cmdset in
|
||||||
|
this custom module.
|
||||||
|
The test command is also a good example of how to use this module in code.
|
||||||
|
|
||||||
"""
|
"""
|
||||||
from ev import syscmdkeys
|
from ev import syscmdkeys
|
||||||
|
|
|
||||||
|
|
@ -7,10 +7,12 @@ This module offers some miscellaneous commands that may be useful
|
||||||
depending on the game you run or the style of administration you
|
depending on the game you run or the style of administration you
|
||||||
prefer. Alternatively they can be looked at for inspiration.
|
prefer. Alternatively they can be looked at for inspiration.
|
||||||
|
|
||||||
To make available in the game, import this module to
|
To make available in the game, make sure to follow the instructions
|
||||||
game.gamesrc.commands.basecmdset.py (or your own equivalent) and add
|
in game/gamesrc/commands/examples.py (copy the template up one level
|
||||||
the command class(es) you want to the default command set. You need to
|
and re-point the relevant settings to this new module - if you already
|
||||||
reload the server to make them recognized.
|
have such a module, you can of course use that). Next import this module into
|
||||||
|
this custom module and add the command class(es) you want to the default
|
||||||
|
command set. You need to reload the server to make them recognized.
|
||||||
"""
|
"""
|
||||||
|
|
||||||
from django.conf import settings
|
from django.conf import settings
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue