<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://manicpop.org/gewiki/index.php?action=history&amp;feed=atom&amp;title=Galaxy_configuration</id>
	<title>Galaxy configuration - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://manicpop.org/gewiki/index.php?action=history&amp;feed=atom&amp;title=Galaxy_configuration"/>
	<link rel="alternate" type="text/html" href="https://manicpop.org/gewiki/index.php?title=Galaxy_configuration&amp;action=history"/>
	<updated>2026-10-20T13:15:22Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.46.2</generator>
	<entry>
		<id>https://manicpop.org/gewiki/index.php?title=Galaxy_configuration&amp;diff=2185&amp;oldid=prev</id>
		<title>Manicpop at 19:02, 18 October 2026</title>
		<link rel="alternate" type="text/html" href="https://manicpop.org/gewiki/index.php?title=Galaxy_configuration&amp;diff=2185&amp;oldid=prev"/>
		<updated>2026-10-18T19:02:25Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Galaxy options control the galaxy&amp;#039;s extent, boundary behavior, and features assigned when a sector is generated. Classic and ge-next defaults are compared in [[Main configuration reference]]; ge-arena uses its own main MSG file. This page explains operational consequences rather than repeating every option&amp;#039;s default.&lt;br /&gt;
&lt;br /&gt;
== Dimensions ==&lt;br /&gt;
&amp;lt;code&amp;gt;UNIVMAX&amp;lt;/code&amp;gt; sets the intended radius in sectors from 0 0. The intended dimensions are therefore &amp;lt;code&amp;gt;(2 × UNIVMAX + 1)&amp;lt;/code&amp;gt; sectors on each axis. Classic GE has an edge error that prevents those intended bounds from working consistently; ge-next corrected it. See [[Classic bug: Galactic perimeter edge errors]] and [[Galactic perimeter]]. Changing the radius after sectors or ships have been stored can leave records outside the new boundary. A new radius should be introduced with a fresh database or documented migration, not a casual live setting change.&lt;br /&gt;
&lt;br /&gt;
ge-arena is different: it sets the radius at match start to five sectors per entering player and wipes the match galaxy afterward. It also scales scanner range to 50% for two players and 75% for three; four or more use the normal range. Later departures do not resize an active match.&lt;br /&gt;
&lt;br /&gt;
== Boundaries ==&lt;br /&gt;
&amp;lt;code&amp;gt;UNIVWRAP&amp;lt;/code&amp;gt; selects wrapping to the opposite edge or the galactic-perimeter response. ge-next 0.3.2 bounds its speed-dependent bounce for small configured galaxies; see [[Galactic perimeter]]. Wrapping does not change which sectors already exist.&lt;br /&gt;
&lt;br /&gt;
== Generated features ==&lt;br /&gt;
&amp;lt;code&amp;gt;PLODDS&amp;lt;/code&amp;gt;, wormhole odds, and nebula settings affect newly generated sectors. Once a sector has been stored, changing odds does not reroll its planets, wormholes, or nebula status. Generation factors are not necessarily direct percentages: a sector can enter the planet-generation branch and still receive no planet. &amp;lt;code&amp;gt;MAXPLSE&amp;lt;/code&amp;gt; sets the maximum body count, but classic generation has an [[Classic bug: MAXPLSE is off by one|off-by-one error]] in that count. See [[Sector]] and [[Wormholes]] for the creation path.&lt;br /&gt;
&lt;br /&gt;
The nebula seed gives a persistent game a repeatable distribution. ge-arena uses a separate in-memory seed for each match. Disabling or changing nebula generation is not a retroactive edit to existing sectors.&lt;br /&gt;
&lt;br /&gt;
== Record limits and sector 0 0 ==&lt;br /&gt;
&amp;lt;code&amp;gt;MAXPLREC&amp;lt;/code&amp;gt; limits growth of the planet database. A generated sector uses a sector record plus records for any planetary bodies. If the limit is reached in classic GE, normal creation can fail; see [[Classic bug: Planet record-limit failure]].&lt;br /&gt;
&lt;br /&gt;
Sector 0 0 and its neutral-zone planets are initialized separately from ordinary random generation. Their names, owners, coordinates, and stock are configured in the main file. See [[Neutral zone]], [[Zygor]], and [[Tahanian Station]].&lt;br /&gt;
&lt;br /&gt;
Before changing a live galaxy, back up the complete database set; see [[Database files]].&lt;br /&gt;
&lt;br /&gt;
{{GE navigation}}&lt;br /&gt;
[[Category:Sysop documentation]]&lt;/div&gt;</summary>
		<author><name>Manicpop</name></author>
	</entry>
</feed>