Change most http links to https

This commit is contained in:
amfl 2021-06-23 20:05:25 +12:00
parent c2c6d8ad50
commit 11fa5fe184
49 changed files with 188 additions and 188 deletions

View file

@ -227,7 +227,7 @@ expected, but they may appear with delays or in groups.
## Further reading
Technically, `run_async` is just a very thin and simplified wrapper around a
[Twisted Deferred](http://twistedmatrix.com/documents/9.0.0/core/howto/defer.html) object; the
[Twisted Deferred](https://twistedmatrix.com/documents/9.0.0/core/howto/defer.html) object; the
wrapper sets
up a default errback also if none is supplied. If you know what you are doing there is nothing
stopping you from bypassing the utility function, building a more sophisticated callback chain after

View file

@ -79,16 +79,16 @@ translations described below.
#### Telnet + GMCP
[GMCP](http://www.gammon.com.au/gmcp), the *Generic Mud Communication Protocol* sends data on the
[GMCP](https://www.gammon.com.au/gmcp), the *Generic Mud Communication Protocol* sends data on the
form `cmdname + JSONdata`. Here the cmdname is expected to be on the form "Package.Subpackage".
There could also be additional Sub-sub packages etc. The names of these 'packages' and 'subpackages'
are not that well standardized beyond what individual MUDs or companies have chosen to go with over
the years. You can decide on your own package names, but here are what others are using:
- [Aardwolf GMCP](http://www.aardwolf.com/wiki/index.php/Clients/GMCP)
- [Discworld GMCP](http://discworld.starturtle.net/lpc/playing/documentation.c?path=/concepts/gmcp)
- [Avatar GMCP](http://www.outland.org/infusions/wiclear/index.php?title=MUD%20Protocols&lang=en)
- [IRE games GMCP](http://nexus.ironrealms.com/GMCP)
- [Aardwolf GMCP](https://www.aardwolf.com/wiki/index.php/Clients/GMCP)
- [Discworld GMCP](https://discworld.starturtle.net/lpc/playing/documentation.c?path=/concepts/gmcp)
- [Avatar GMCP](https://www.outland.org/infusions/wiclear/index.php?title=MUD%20Protocols&lang=en)
- [IRE games GMCP](https://nexus.ironrealms.com/GMCP)
Evennia will translate underscores to `.` and capitalize to fit the specification. So the
outputcommand `foo_bar` will become a GMCP command-name `Foo.Bar`. A GMCP command "Foo.Bar" will be
@ -167,4 +167,4 @@ same example `("cmdname", ("arg",), {})` will be sent/received as a valid JSON s
["cmdname, ["arg"], {}]
Since JSON is native to Javascript, this becomes very easy for the webclient to handle.
Since JSON is native to Javascript, this becomes very easy for the webclient to handle.

View file

@ -42,8 +42,8 @@ The `v()` function returns the `HELLO_VALUE.D` attribute on the object that the
If you are still curious about how Softcode works, take a look at some external resources:
- http://www.tinymux.com/wiki/index.php/Softcode
- http://www.duh.com/discordia/mushman/man2x1
- https://wiki.tinymux.org/index.php/Softcode
- https://www.duh.com/discordia/mushman/man2x1
## Problems with Softcode
@ -91,4 +91,4 @@ satisfy most creative builders. However, if you really, *really* want to offer o
is of course nothing stopping you from adding that to Evennia, no matter our recommendations. You
could even re-implement MUX' softcode in Python should you be very ambitious. The
[in-game-python](../Contribs/Dialogues-in-events) is an optional
pseudo-softcode plugin aimed at developers wanting to script their game from inside it.
pseudo-softcode plugin aimed at developers wanting to script their game from inside it.

View file

@ -63,4 +63,4 @@ Note that having to try several different encodings every input/output adds
unneccesary overhead. Try to guess the most common encodings you players will
use and make sure these are tried first. The International *UTF-8* encoding is
what Evennia assumes by default (and also what Python/Django use normally). See
the Wikipedia article [here](http://en.wikipedia.org/wiki/Text_encodings) for more help.
the Wikipedia article [here](https://en.wikipedia.org/wiki/Text_encodings) for more help.

View file

@ -6,10 +6,10 @@ you could emulate that with Evennia. If you are ambitious you could even design
perfectly fitting your own dreams of the ideal game.
We do offer a default however. The default Evennia setup tends to *resemble*
[MUX2](http://www.tinymux.org/), and its cousins [PennMUSH](http://www.pennmush.org),
[TinyMUSH](http://tinymush.sourceforge.net/), and [RhostMUSH](http://www.rhostmush.org/). While the
reason for this similarity is partly historical, these codebases offer very mature feature sets for
administration and building.
[MUX2](https://www.tinymux.org/), and its cousins [PennMUSH](https://www.pennmush.org),
[TinyMUSH](https://github.com/TinyMUSH/TinyMUSH/wiki), and [RhostMUSH](http://www.rhostmush.com/).
While the reason for this similarity is partly historical, these codebases offer very mature feature
sets for administration and building.
Evennia is *not* a MUX system though. It works very differently in many ways. For example, Evennia
deliberately lacks an online softcode language (a policy explained on our [softcode policy
@ -82,4 +82,4 @@ something to the effect of
if not self.args:
self.caller.msg("Usage: nick[/switches] <nickname> = [<string>]")
return
```
```