Rename all instances of Player->Account.

evennia/server/profiling/dummyrunner.py

@@ -15,7 +15,7 @@ full step-by-step setup help.
 Basically (for testing default Evennia):
 
  - Use an empty/testing database.
- - set PERMISSION_PLAYER_DEFAULT = "Builder"
+ - set PERMISSION_ACCOUNT_DEFAULT = "Builder"
  - start server, eventually with profiling active
  - launch this client runner
 
@@ -65,7 +65,7 @@ TIMESTEP = DUMMYRUNNER_SETTINGS.TIMESTEP
 # chance of a client performing an action, per timestep. This helps to
 # spread out usage randomly, like it would be in reality.
 CHANCE_OF_ACTION = DUMMYRUNNER_SETTINGS.CHANCE_OF_ACTION
-# spread out the login action separately, having many players create accounts
+# spread out the login action separately, having many accounts create accounts
 # and connect simultaneously is generally unlikely.
 CHANCE_OF_LOGIN = DUMMYRUNNER_SETTINGS.CHANCE_OF_LOGIN
 # Port to use, if not specified on command line
@@ -79,7 +79,7 @@ NLOGGED_IN = 0
 
 INFO_STARTING = \
     """
-    Dummyrunner starting using {N} dummy player(s). If you don't see
+    Dummyrunner starting using {N} dummy account(s). If you don't see
     any connection messages, make sure that the Evennia server is
     running.
 
@@ -95,7 +95,7 @@ ERROR_NO_MIXIN = \
         from evennia.server.profiling.settings_mixin import *
 
     This will change the settings in the following way:
-        - change PERMISSION_PLAYER_DEFAULT to 'Developer' to allow clients
+        - change PERMISSION_ACCOUNT_DEFAULT to 'Developer' to allow clients
           to test all commands
         - change PASSWORD_HASHERS to use a faster (but less safe) algorithm
           when creating large numbers of accounts at the same time
@@ -106,7 +106,7 @@ ERROR_NO_MIXIN = \
     error completely.
 
     Warning: Don't run dummyrunner on a production database! It will
-    create a lot of spammy objects and player accounts!
+    create a lot of spammy objects and account accounts!
     """
 
 
@@ -121,7 +121,7 @@ HELPTEXT = """
 DO NOT RUN THIS ON A PRODUCTION SERVER! USE A CLEAN/TESTING DATABASE!
 
 This stand-alone program launches dummy telnet clients against a
-running Evennia server. The idea is to mimic real players logging in
+running Evennia server. The idea is to mimic real accounts logging in
 and repeatedly doing resource-heavy commands so as to stress test the
 game. It uses the default command set to log in and issue commands, so
 if that was customized, some of the functionality will not be tested
@@ -136,9 +136,9 @@ Setup:
      `evennia migrate`)
   2) in server/conf/settings.py, add
 
-        PERMISSION_PLAYER_DEFAULT="Builder"
+        PERMISSION_ACCOUNT_DEFAULT="Builder"
 
-     This is so that the dummy players can test building operations.
+     This is so that the dummy accounts can test building operations.
      You can also customize the dummyrunner by modifying a setting
      file specified by DUMMYRUNNER_SETTINGS_MODULE
 
@@ -160,12 +160,12 @@ Setup:
 
 Notes:
 
-The dummyrunner tends to create a lot of players all at once, which is
+The dummyrunner tends to create a lot of accounts all at once, which is
 a very heavy operation. This is not a realistic use-case - what you want
 to test is performance during run. A large
 number of clients here may lock up the client until all have been
 created. It may be better to connect multiple dummyrunners instead of
-starting one single one with a lot of players. Exactly what this number
+starting one single one with a lot of accounts. Exactly what this number
 is depends on your computer power. So start with 10-20 clients and increase
 until you see the initial login slows things too much.
 
@@ -223,7 +223,7 @@ def makeiter(obj):
 class DummyClient(telnet.StatefulTelnetProtocol):
     """
     Handles connection to a running Evennia server,
-    mimicking a real player by sending commands on
+    mimicking a real account by sending commands on
     a timer.
 
     """