mirror of
https://github.com/evennia/evennia.git
synced 2026-03-16 21:06:30 +01:00
Resync all links and fix issues with auto-relink
This commit is contained in:
parent
20a1741f4c
commit
fab769e0d0
107 changed files with 887 additions and 877 deletions
|
|
@ -49,7 +49,7 @@ representation in the game world. Through their Account they can instead choose
|
|||
[puppet](Glossary#puppet) one (or more, depending on game mode) [Characters](Glossary#character) in
|
||||
the game.
|
||||
|
||||
In the default [multisession mode](Sessions#multisession-mode) of Evennia, you immediately start
|
||||
In the default [multisession mode](Component/Sessions#multisession-mode) of Evennia, you immediately start
|
||||
puppeting a Character with the same name as your Account when you log in - mimicking how older
|
||||
servers used to work.
|
||||
|
||||
|
|
@ -65,8 +65,8 @@ reachable from the `admin` link on the default Evennia website you get with your
|
|||
The term _Attribute_ should not be confused with ([properties](Glossary#property) or
|
||||
[fields](Glossary#field). The `Attribute` represents arbitrary pieces of data that can be attached
|
||||
to any [typeclassed](Glossary#typeclass) entity in Evennia. Attributes allows storing new persistent
|
||||
data on typeclasses without changing their underlying database schemas. [Read more about Attributes
|
||||
here](Attributes).
|
||||
data on typeclasses without changing their underlying database schemas.
|
||||
[Read more about Attributes here](Component/Attributes).
|
||||
|
||||
### _channel_
|
||||
|
||||
|
|
@ -82,7 +82,7 @@ comm system here](Communications#channels).
|
|||
The _Character_ is the term we use for the default avatar being [puppeted](Glossary#puppet) by the
|
||||
[account](Glossary#account) in the game world. It is represented by the `Character` typeclass (which
|
||||
is a child of [Object](Glossary#object)). Many developers use children of this class to represent
|
||||
monsters and other NPCs. You can [read more about it here](Objects#subclasses-of-object).
|
||||
monsters and other NPCs. You can [read more about it here](Component/Objects#subclasses-of-object).
|
||||
|
||||
### _django_
|
||||
|
||||
|
|
@ -99,7 +99,7 @@ There is usually no need to know the details of Django's database handling in or
|
|||
it will handle most of the complexity for you under the hood using what we call
|
||||
[typeclasses](Glossary#typeclass). But should you need the power of Django you can always get it.
|
||||
Most commonly people want to use "raw" Django when doing more advanced/custom database queries than
|
||||
offered by Evennia's [default search functions](Tutorial-Searching-For-Objects). One will then need
|
||||
offered by Evennia's [default search functions](Howto/StartingTutorial/Tutorial-Searching-For-Objects). One will then need
|
||||
to read about Django's _querysets_. Querysets are Python method calls on a special form that lets
|
||||
you build complex queries. They get converted into optimized SQL queries under the hood, suitable
|
||||
for your current database. [Here is our tutorial/explanation of Django queries](Tutorial-Searching-
|
||||
|
|
@ -133,7 +133,7 @@ A _field_ or _database field_ in Evennia refers to a [property](Glossary#propert
|
|||
properties per typeclass are database fields but they are often tied to the core functionality of
|
||||
that base typeclass (for example [Objects](Glossary#object) store its location as a field). In all
|
||||
other cases, [attributes](Glossary#attribute) are used to add new persistent data to the typeclass.
|
||||
[Read more about typeclass properties here](Typeclasses#about-typeclass-properties).
|
||||
[Read more about typeclass properties here](Component/Typeclasses#about-typeclass-properties).
|
||||
|
||||
### _git_
|
||||
|
||||
|
|
@ -166,8 +166,8 @@ Common usage (for non-Evennia developers):
|
|||
you 'download' Evennia. You only need to do this once.
|
||||
- `git pull` (inside local copy of repository) - sync your local repository with what is online.
|
||||
|
||||
> Full usage of Git is way beyond the scope of this glossary. See [Tutorial - version
|
||||
control](Version-Control) for more info and links to the Git documentation.
|
||||
> Full usage of Git is way beyond the scope of this glossary. See
|
||||
[Tutorial - version control](Coding/Version-Control) for more info and links to the Git documentation.
|
||||
|
||||
### _migrate_
|
||||
|
||||
|
|
@ -179,7 +179,7 @@ latest changes, just `cd` into your game dir and run
|
|||
evennia migrate
|
||||
|
||||
That should be it (see [virtualenv](Glossary#virtualenv) if you get a warning that the `evennia`
|
||||
command is not available). See also [Updating your game](Updating-Your-Game) for more details.
|
||||
command is not available). See also [Updating your game](Coding/Updating-Your-Game) for more details.
|
||||
|
||||
> Technically, migrations are shipped as little Python snippets of code that explains which database
|
||||
actions must be taken to upgrade from one version of the schema to the next. When you run the
|
||||
|
|
@ -211,8 +211,7 @@ try to use `object` to refer to the general term and capitalized `Object` when w
|
|||
typeclass.
|
||||
|
||||
The `Object` is a typeclass that represents all *in-game* entities, including
|
||||
[Characters](Glossary#character), rooms, trees, weapons etc. [Read more about Objects
|
||||
here](Objects).
|
||||
[Characters](Glossary#character), rooms, trees, weapons etc. [Read more about Objects here](Component/Objects).
|
||||
|
||||
### _pip_
|
||||
|
||||
|
|
@ -265,16 +264,16 @@ well.
|
|||
|
||||
### _script_
|
||||
|
||||
When we refer to _Scripts_, we generally refer to the `Script` [typeclass](Typeclasses). Scripts are
|
||||
When we refer to _Scripts_, we generally refer to the `Script` [typeclass](Component/Typeclasses). Scripts are
|
||||
the mavericks of Evennia - they are like [Objects](Glossary#object) but without any in-game
|
||||
existence. They are useful as custom places to store data but also as building blocks in persistent
|
||||
game systems. Since the can be initialized with timing capabilities they can also be used for long-
|
||||
time persistent time keeping (for fast updates other types of timers may be better though). [Read
|
||||
more about Scripts here](Scripts)
|
||||
time persistent time keeping (for fast updates other types of timers may be better though).
|
||||
[Read more about Scripts here](Component/Scripts)
|
||||
|
||||
### _session_
|
||||
|
||||
A [Session](Sessions) is a Python object representing a single client connection to the server. A
|
||||
A [Session](Component/Sessions) is a Python object representing a single client connection to the server. A
|
||||
given human player could connect to the game from different clients and each would get a Session
|
||||
(even if you did not allow them to actually log in and get access to an
|
||||
[account](Glossary#account)).
|
||||
|
|
@ -285,7 +284,7 @@ can be useful for certain game states.
|
|||
|
||||
### _ticker_
|
||||
|
||||
The [Ticker handler](TickerHandler) runs Evennia's optional 'ticker' system. In other engines, such
|
||||
The [Ticker handler](Component/TickerHandler) runs Evennia's optional 'ticker' system. In other engines, such
|
||||
as [DIKU](https://en.wikipedia.org/wiki/DikuMUD), all game events are processed only at specific
|
||||
intervals called 'ticks'. Evennia has no such technical limitation (events are processed whenever
|
||||
needed) but using a fixed tick can still be useful for certain types of game systems, like combat.
|
||||
|
|
@ -294,7 +293,7 @@ to be called when those ticks come around.
|
|||
|
||||
### _typeclass_
|
||||
|
||||
The [typeclass](Typeclasses) is an Evennia-specific term. A typeclass allows developers to work with
|
||||
The [typeclass](Component/Typeclasses) is an Evennia-specific term. A typeclass allows developers to work with
|
||||
database-persistent objects as if they were normal Python objects. It makes use of specific
|
||||
[Django](Glossary#django) features to link a Python class to a database table. Sometimes we refer to
|
||||
such code entities as _being typeclassed_.
|
||||
|
|
@ -369,4 +368,4 @@ console/terminal.
|
|||
|
||||
So, when do I *need* to activate my virtualenv? If the virtualenv is not active, none of the Python
|
||||
packages/programs you installed in it will be available to you. So at a minimum, *it needs to be
|
||||
activated whenever you want to use the `evennia` command* for any reason.
|
||||
activated whenever you want to use the `evennia` command* for any reason.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue