Permalink
Browse files

Update some links to refer to https.

  • Loading branch information...
shawnw committed Jun 24, 2018
1 parent f7a630c commit 76946f613e003b33cebe5230bbba2ddd3640dafe
Showing with 57 additions and 20 deletions.
  1. +2 −2 FAQ.md
  2. +1 −1 INSTALL.md
  3. +2 −2 README.md
  4. +1 −1 UPGRADING.md
  5. +41 −4 htmldocs/CHANGES.187.html
  6. +3 −3 htmldocs/FAQ.html
  7. +2 −2 htmldocs/INSTALL.html
  8. +3 −3 htmldocs/README.html
  9. +2 −2 htmldocs/UPGRADING.html
4 FAQ.md
@@ -63,7 +63,7 @@ Where can I get more information about admin'ing and hacking MUSH?
==================================================================
Read
[Javelin's God for PennMUSH Gods](http://download.pennmush.org/Guide/),
[Javelin's God for PennMUSH Gods](https://download.pennmush.org/Guide/),
loads of info about setting up a MUSH, hacking source code, daily
maintenance, and many tips from other Gods! It's a bit dated in some
respects but still very useful.
@@ -73,7 +73,7 @@ and reference material for working with mush hardcode that are
slightly less out of date.
The source code has
[doxygen documentation](http://doxygen.pennmush.org) that can be
[doxygen documentation](https://doxygen.pennmush.org) that can be
browsed.
Where can I hear about new releases?
@@ -23,7 +23,7 @@ resources will be written with UNIX is mind.)
You may also want to take a look at the Managing PennMUSH book at
<http://community.pennmush.org> and at Javelin's Guide for PennMUSH
Gods, at <http://download.pennmush.org/Guide/guide-single.html>
Gods, at <https://download.pennmush.org/Guide/guide-single.html>
Important background
====================
@@ -8,7 +8,7 @@ depending on whether it's a new install or an upgrade. The file
[I18N](I18N.html) discusses internationalization.
You may also want to take a look at Javelin's Guide for PennMUSH Gods,
at <http://download.pennmush.org/Guide/>
at <https://download.pennmush.org/Guide/>
Introduction and history
========================
@@ -74,7 +74,7 @@ codebase that it is today.
If you are planning on modifying the source code to PennMUSH, you'll
probably want Javelin's Guide for PennMUSH Gods, which should be
available where you got this code, or, in hypertext, as
<http://download.pennmush.org/Guide/guide-single.html>. More recent
<https://download.pennmush.org/Guide/guide-single.html>. More recent
versions may be available at <http://community.pennmush.org>.
Enjoy!
@@ -40,7 +40,7 @@ To upgrade with patch files, get all the patch files for higher
patchlevels than your current version. For example, if you're running
1.8.0p0 and the latest version is 1.8.0p4, you need patches 1-4.
Patchfiles can be downloaded via <http://download.pennmush.org/Source/>
Patchfiles can be downloaded via <https://download.pennmush.org/Source/>
and are usually named things like 1.8.0-patch02 (the patch from 1.8.0p1
to 1.8.0p2) or, in some cases, 1.7.6p16-1.8.0p0.patch (the patch from
1.7.6p16 to 1.8.0p0).
@@ -12,7 +12,7 @@
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<link rel="stylesheet" href="mushdoc.css">
<link rel="stylesheet" href="mushdoc.css" />
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
@@ -27,6 +27,7 @@ <h1 class="title">PennMUSH 1.8.7 Changes</h1>
<ul>
<li><a href="#version-1.8.7-patchlevel-0-20">Version 1.8.7 patchlevel 0 ??? ?? 20??</a><ul>
<li><a href="#major-changes">Major Changes</a></li>
<li><a href="#minor-changes">Minor Changes</a></li>
<li><a href="#softcode">Softcode</a></li>
<li><a href="#fixes">Fixes</a></li>
<li><a href="#documentation">Documentation</a></li>
@@ -40,6 +41,7 @@ <h1 class="title">PennMUSH 1.8.7 Changes</h1>
<li>[GM] is Greg Millam, a PennMUSH developer (aka Walker)</li>
<li>[MG] is Mike Griffiths, a PennMUSH developer (aka Talvo)</li>
<li>[TK] is Tim Krajcar, a PennMUSH developer (aka Rince)</li>
<li>[MT] is Mike Taylor, a PennMUSH developer (aka Qon or Zenithar)</li>
<li>[3] refers to code by (or inspired by) TinyMUSH 3.0</li>
<li>[MUX] refers to code by (or inspired by) TinyMUX 2.x</li>
<li>[Rhost] refers to code by (or inspired by) RhostMUSH</li>
@@ -49,27 +51,62 @@ <h1 class="title">PennMUSH 1.8.7 Changes</h1>
<h1 id="version-1.8.7-patchlevel-0-20">Version 1.8.7 patchlevel 0 ??? ?? 20??</h1>
<h2 id="major-changes">Major Changes</h2>
<ul>
<li>Support websocket connections. See <a href="http://grapenut.org/code/wsclient/index.html" class="uri">http://grapenut.org/code/wsclient/index.html</a> for a sample in-browser client. [Grapenut, 1007]</li>
<li>Support websocket connections. See <a href="https://github.com/grapenut/websockclient" class="uri">https://github.com/grapenut/websockclient</a> for a sample in-browser client. [Grapenut, 1007]</li>
<li>Change attributes from being stored in sorted linked lists to sorted arrays; results in faster lookups and less memory usage. [SW]</li>
</ul>
<h2 id="minor-changes">Minor Changes</h2>
<ul>
<li>Message translation support now defaults to off. Run configure with <code>--enable-nls</code> to turn it on if needed. [SW]</li>
<li>Shrink the <code>NEW_PE_INFO</code> struct, for signficant memory savings in softcode that queues lots of commands. [SW]</li>
<li>Add more test cases to the softcode test suite. [SW]</li>
<li>log_forces in mushcnf.dost now defaults to no. You probably only want this on if you're debugging. [MG]</li>
</ul>
<h2 id="softcode">Softcode</h2>
<ul>
<li>Support all of Rhost's colors() key arguments (Except n). [SW, 1112]</li>
<li>Support all of Rhost's <code>colors()</code> key arguments (Except n). [SW, 1112]</li>
<li>Functions that work on integers (Like <code>div()</code> or <code>band()</code>) now use 64-bit values instead of 32-bit. [SW]</li>
<li><code>json_query()</code> get and exists can follow paths into objects instead of taking a single key/index. Suggested by qa'toq. [SW]</li>
<li><code>json_query(str, unescape)</code> handles unicode escape sequences.</li>
<li><code>json(string, foo)</code> escapes non-ascii characters.</li>
<li><code>clone()</code> now takes an optional fourth argument to act like <code>@clone/preserve</code> [797]</li>
<li>New 'me' and 'inventory' flags for <code>scan()</code> give finer control of what to scan. [MG]</li>
<li><code>orflags()</code>, <code>orlflags()</code>, <code>andflags()</code>, <code>andlflags()</code>, and the power versions no longer return errors on unknown flags/powers. They instead treat the unknown one as if it wasn't set. Suggested by Qon. [1180].</li>
<li>Side-effect version of link() now returns 1 on success, 0 or #-1 on failure. [MT]</li>
<li>owner() now accepts two optional arguments, allowing ownership to be changed as in <span class="citation" data-cites="chown">@chown</span> and <span class="citation" data-cites="atrchown">@atrchown</span>. [MT]</li>
<li><code>@chatformat</code> now receives a new arg, <code>%6</code>, which defaults to &quot;says&quot; but may be replaced by the speechtext mogrifier. Inspired by Bodin. [MG]</li>
</ul>
<h2 id="fixes">Fixes</h2>
<ul>
<li>A bunch of color names weren't mapping correctly to Xterm color codes. [SW]</li>
<li><code>@grep/iprint</code> hilites the matching text in the same case it appears in the attribute body. [SW, 1120]</li>
<li><code>@mail</code> wasn't updating a player's MAILCURF attribute correctly. [CLDawes, 1131]</li>
<li>Connecting with a web browser to a mush without a <code>mud_url</code> config option set caused an infinite refresh loop. Reported by grapenut. [1149]</li>
<li>Make sure <code>sigrecv_ack()</code> won't hang the mush if it somehow gets called at the wrong time. Also fix a file descriptor leak in the signal handling code. [SW]</li>
<li>Pass <code>pe_info</code> into IDLE and HAVEN attributes from the page command. [MG]</li>
<li>The x and X options to <code>align()</code> now always truncate to the column width, rather than incorrectly truncating at a space. Reported by Qon. [MG, 1178]</li>
<li><code>json_query()</code> didn't understand an action of 'type' as documented. [SW]</li>
<li>Assorted help file fixes. [SW]</li>
<li><code>@clone</code> without /preserve wasn't stripping privileged flags and such. [1190,SW]</li>
<li><code>@chown/preserve</code> was resetting wiz-bit despite it's help file indicating otherwise. [1187] PR by Qon.</li>
<li><code>scan()</code> now determines if objects will be included based on whether the caller can examine them, rather than if <code>scan()</code>'s <code>&lt;looker&gt;</code> can examine them. [MG]</li>
<li>Fixed some bugs regarding when <code>setq()</code> will and won't let you set the values of named registers when you've hit the limit. [MG, 1179]</li>
<li>Fix an off-by-one error in command switch initialization code. [SW]</li>
</ul>
<h2 id="documentation">Documentation</h2>
<ul>
<li>Changelogs and other documentation use markup. [SW, 1140]</li>
<li>Start trying to clean up and revise ancient documentation. [1095]</li>
<li>Minor help fixes. [MG]</li>
<li>More minor help fixes. [MT]</li>
</ul>
<h2 id="os-specific">OS Specific</h2>
<h3 id="bsds-in-general">BSDs in general</h3>
<ul>
<li><code>info_slave</code> and <code>ssl_slave</code> use <code>kqueue()</code> to efficiently be notified of parent mush crashes.</li>
</ul>
<h3 id="openbsd">OpenBSD</h3>
<ul>
<li>netmush and slave processes use pledge(2) to limit their privileges. [SW]</li>
<li>netmush and slave processes use <code>pledge(2)</code> to limit their privileges. [SW]</li>
</ul>
<h3 id="windows">Windows</h3>
<ul>
@@ -11,7 +11,7 @@
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<link rel="stylesheet" href="mushdoc.css">
<link rel="stylesheet" href="mushdoc.css" />
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
@@ -52,9 +52,9 @@ <h1 id="how-do-i-request-a-new-feature">How do I request a new feature?</h1>
<p>Visit the <a href="https://github.com/pennmush/pennmush/issues">issue tracker</a>.</p>
<p>No promises, but we try to get back to you about the feasibility of suggestions quickly, and implement them as we can. Features that come with a patch implementing them tend to get accepted faster than those that don't unless it's a trivial addition.</p>
<h1 id="where-can-i-get-more-information-about-admining-and-hacking-mush">Where can I get more information about admin'ing and hacking MUSH?</h1>
<p>Read <a href="http://download.pennmush.org/Guide/">Javelin's God for PennMUSH Gods</a>, loads of info about setting up a MUSH, hacking source code, daily maintenance, and many tips from other Gods! It's a bit dated in some respects but still very useful.</p>
<p>Read <a href="https://download.pennmush.org/Guide/">Javelin's God for PennMUSH Gods</a>, loads of info about setting up a MUSH, hacking source code, daily maintenance, and many tips from other Gods! It's a bit dated in some respects but still very useful.</p>
<p>The <a href="http://community.pennmush.org">community portal</a> also has guides and reference material for working with mush hardcode that are slightly less out of date.</p>
<p>The source code has <a href="http://doxygen.pennmush.org">doxygen documentation</a> that can be browsed.</p>
<p>The source code has <a href="https://doxygen.pennmush.org">doxygen documentation</a> that can be browsed.</p>
<h1 id="where-can-i-hear-about-new-releases">Where can I hear about new releases?</h1>
<p>New releases of the PennMUSH code are announced on <code>M*U*S*H</code> (mush.pennmush.org 4201).</p>
<h1 id="why-doesnt-t-or-space-work-right-for-pueblo-clients">Why doesn't %t or space() work right for Pueblo clients?</h1>
@@ -11,7 +11,7 @@
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<link rel="stylesheet" href="mushdoc.css">
<link rel="stylesheet" href="mushdoc.css" />
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
@@ -36,7 +36,7 @@ <h1 id="introduction">Introduction</h1>
</ol>
<p>If you are upgrading from a previous PennMUSH release, this is probably not the file you want to start with. Read the <a href="UPGRADING.html">UPGRADING.md</a> file first.</p>
<p><strong>DISCLAIMER</strong>: Before attempting to run a MUD of any sort, you should have some reasonable knowledge of UNIX and C. If you do not, it is <em>strongly</em> suggested that you learn UNIX and C to some reasonable level of competency before attempting to set up a MUSH. (Note that even people using the Windows ports are encouraged to know UNIX, because that's the paradigm that PennMUSH was built with, and most resources will be written with UNIX is mind.)</p>
<p>You may also want to take a look at the Managing PennMUSH book at <a href="http://community.pennmush.org" class="uri">http://community.pennmush.org</a> and at Javelin's Guide for PennMUSH Gods, at <a href="http://download.pennmush.org/Guide/guide-single.html" class="uri">http://download.pennmush.org/Guide/guide-single.html</a></p>
<p>You may also want to take a look at the Managing PennMUSH book at <a href="http://community.pennmush.org" class="uri">http://community.pennmush.org</a> and at Javelin's Guide for PennMUSH Gods, at <a href="https://download.pennmush.org/Guide/guide-single.html" class="uri">https://download.pennmush.org/Guide/guide-single.html</a></p>
<h1 id="important-background">Important background</h1>
<p>Here's a quick picture of the organization of the MUSH directory tree. The &quot;src&quot; directory contains C source code. The &quot;hdrs&quot; directory contains header files for the source code. The files used by a running MUSH are in the &quot;game&quot; directory, which includes subdirectories &quot;data&quot; (current databases), &quot;txt&quot; (text files and directories for building them), &quot;log&quot; (log files), and &quot;save&quot; (backup databases). Finally, the &quot;hints&quot; directory is used during the installation process, the &quot;test&quot; directory contains an automated regression testing suite, and the &quot;po&quot; directory holds translation message files.</p>
<pre><code>pennmush--+-&gt; src
@@ -11,7 +11,7 @@
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<link rel="stylesheet" href="mushdoc.css">
<link rel="stylesheet" href="mushdoc.css" />
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
@@ -32,7 +32,7 @@ <h1 class="title">User's Guide to PennMUSH 1.8.x</h1>
</nav>
<p>PennMUSH is a server used to create text-based multiplayer games.</p>
<p>Installation information can be found in the files <a href="INSTALL.html">INSTALL.md</a> or <a href="UPGRADING.html">UPGRADING.md</a>, depending on whether it's a new install or an upgrade. The file <a href="I18N.html">I18N</a> discusses internationalization.</p>
<p>You may also want to take a look at Javelin's Guide for PennMUSH Gods, at <a href="http://download.pennmush.org/Guide/" class="uri">http://download.pennmush.org/Guide/</a></p>
<p>You may also want to take a look at Javelin's Guide for PennMUSH Gods, at <a href="https://download.pennmush.org/Guide/" class="uri">https://download.pennmush.org/Guide/</a></p>
<h1 id="introduction-and-history">Introduction and history</h1>
<p>PennMUSH uses a version-numbering system that includes version numbers (like 1.7.2) and patchlevels (like p32), usually written together (1.7.2p32).</p>
<p>PennMUSH is a TinyMUD derivative, and one of the branches along the MUSH line. &quot;Vanilla&quot; TinyMUSH, which added the &quot;v&quot; registers and functions to the basic TinyMUD building commands, was written by Larry Foard. The code was later expanded by Jin, of MicroMUSH. In January of 1991, MicroMUSH changed its name to MicroMUSE, and the code there continued to develop under the MUSE name. At that same point in time, Moonchilde took the last public release of that code and began a series of improvements and extensions.</p>
@@ -43,7 +43,7 @@ <h1 id="introduction-and-history">Introduction and history</h1>
<p>In August of 1997, Ralph Melton left the PennMUSH development team, and Thorvald Natvig joined as a new member. Many thanks go to Ralph who contributed much time, code, and good cheer to PennMUSH. Since that time, the development team has gained and lost members. The current membership is usually listed at the top of the latest CHANGES.<version> file.</p>
<p>In November 2002, with the release of PennMUSH 1.7.6, PennMUSH began using the Artistic License (see the COPYRITE file), an open source/free software license. This license was simultaneously adopted by TinyMUSH (2.2.5, 3.x) and TinyMUX to facilitate code sharing and widen use.</p>
<p>In July 2006, Javelin retired from the role of Maintainer, passing the mantle of lead developer to Raevnos. Many thanks go to Javelin whose contributions and guidance of PennMUSH have shaped it into the codebase that it is today.</p>
<p>If you are planning on modifying the source code to PennMUSH, you'll probably want Javelin's Guide for PennMUSH Gods, which should be available where you got this code, or, in hypertext, as <a href="http://download.pennmush.org/Guide/guide-single.html" class="uri">http://download.pennmush.org/Guide/guide-single.html</a>. More recent versions may be available at <a href="http://community.pennmush.org" class="uri">http://community.pennmush.org</a>.</p>
<p>If you are planning on modifying the source code to PennMUSH, you'll probably want Javelin's Guide for PennMUSH Gods, which should be available where you got this code, or, in hypertext, as <a href="https://download.pennmush.org/Guide/guide-single.html" class="uri">https://download.pennmush.org/Guide/guide-single.html</a>. More recent versions may be available at <a href="http://community.pennmush.org" class="uri">http://community.pennmush.org</a>.</p>
<p>Enjoy!</p>
<h1 id="getting-help-reporting-bugs">Getting Help, Reporting Bugs</h1>
<p>Here are some guidelines about where and how to report bugs or problems or generally look for help.</p>
@@ -11,7 +11,7 @@
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
</style>
<link rel="stylesheet" href="mushdoc.css">
<link rel="stylesheet" href="mushdoc.css" />
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
@@ -48,7 +48,7 @@ <h1 id="vanilla-upgrade">Vanilla upgrade</h1>
<h2 id="upgrading-with-patch-files">Upgrading with patch files</h2>
<p>This is the easiest way to upgrade your source code if you're keeping up with patches as they come out, or if you're upgrading patchlevels within a release (e.g., within 1.8.0).</p>
<p>To upgrade with patch files, get all the patch files for higher patchlevels than your current version. For example, if you're running 1.8.0p0 and the latest version is 1.8.0p4, you need patches 1-4.</p>
<p>Patchfiles can be downloaded via <a href="http://download.pennmush.org/Source/" class="uri">http://download.pennmush.org/Source/</a> and are usually named things like 1.8.0-patch02 (the patch from 1.8.0p1 to 1.8.0p2) or, in some cases, 1.7.6p16-1.8.0p0.patch (the patch from 1.7.6p16 to 1.8.0p0).</p>
<p>Patchfiles can be downloaded via <a href="https://download.pennmush.org/Source/" class="uri">https://download.pennmush.org/Source/</a> and are usually named things like 1.8.0-patch02 (the patch from 1.8.0p1 to 1.8.0p2) or, in some cases, 1.7.6p16-1.8.0p0.patch (the patch from 1.7.6p16 to 1.8.0p0).</p>
<p>Each patch file contains instructions at the top explaining how to apply it. <strong>FOLLOW THESE!</strong> Don't assume they're all the same. The options to use with the patch program change, and sometimes further steps are required.</p>
<p>After you've applied all the patches and followed all the instructions, you should be good to go. In most cases, you can simply <code>@shutdown/reboot</code> after the final successful compile. If <code>@shutdown/reboot</code> crashes, you'll have to restart again.</p>
<h2 id="using-git">Using git</h2>

0 comments on commit 76946f6

Please sign in to comment.