ASSS Wiki - User contributions [en]

Wormhole

2008-08-05T12:16:57Z

Dr Brain: Added link to physics

A '''wormhole''' is a special tile on a [[map]] that attracts ships and weapons. It will absorb weapons and will drop ships elsewhere that it sucks in. Different ships have different gravity settings so that some can be more resistant to wormholes than others.

You can change a wormhole's animation by replacing over5.bm2 withan [[LVZ]]. Also note the trick with wormholes used in [[Hyperspace]].

See [[Physics]] for the gravity formula.

[[Category:Map]]

Physics

2008-08-05T12:16:04Z

Dr Brain: Added wormhole physics

[[SubSpace]] works on its own special unit scales. This is a collection of observed units and other special physics that SubSpace uses.

; Bounce Formula : SpeedAfter = SpeedBefore * (16 / BounceFactor) (See [[Misc Settings]].)

; Rotation : 90Â° rotation in 1/100th of a second, ''ie: Set rotation to 400, can do a full rotation of 360Â° in one second.''

:: In packets, rotation of a player's ship is a number 0-39... where 0 is straight up and proceeding clockwise. This corresponds to which of the 40 degree graphics to display.

: degrees per tick = rotation_setting / 1000

; Speed : Pixels traveled in 10 seconds.

: pixels per tick = speed_setting / 1000

; Thrust : '''Speed''' increased every 1/100th of a second.

:: ''Sample: Thrust of 10 applied for a second increases your speed by 1000''

; Tick : 1/100th of a second, ''i.e. 0.01s or 10ms.''

; Recharge : Amount of energy units gained in 10 seconds.

; Ball Friction : The amount subtracted from a timer per tick. This timer is initialised to 1 million when the ball is fired, and multiplied with the ball x and y speeds separately on each tick. See also [[Ball Friction]].

; Gravity : The amount of velocity applied per tick (thrust) is 1000*Gravity/(Distance^2) where Distance is the distance between the player and the [[Wormhole]] in pixels. GravityTopSpeed will be added to a player's top speed as long as at least one Wormhole is applying a thrust of 1 or more. The tile radius of the top speed effect is tiles=1.976*(g^.5).
[[Category:Game Intricacies]]

Hyperspace

2005-03-25T04:55:34Z

Dr Brain: Filled in some of the more recent history

SSCX-A Hyperspace was one of the first zones to adopt [[ASSS]].

== Gameplay ==

== Staff ==

<table border=0 frame=void rules=cols width=50%>
<tr>
<td align=center colspan=3><h3>Sysops</h3></td>
</tr>
<tr>
<td align=center>[[User:Dr Brain|Dr Brain]]</td>
<td align=center>Picano</td>
</tr>
</table>

<table border=0 frame=void rules=cols width=50%>
<tr>
<td align=center colspan=3><h3>Smods</h3></td>
</tr>
<tr>
<td align=center>D1st0rt</td>
</tr>
</table>

<table border=0 frame=void rules=cols width=50%>
<tr>
<td align=center colspan=4><h3>Moderators</h3></td>
</tr>
<tr>
<td align=center>Coenny</td>
<td align=center>Quigybobo</td>
<td align=center>FunkmastaD</td>
<td align=center>Lanvalk</td>
</tr>
</table>

== History ==

=== Event Horizon ===

Hyperspace started life as a LAN zone played by a small group of friends, Dr Brain among them. They eventually decided to put it online to try and get more players in it. Having something of a scientific bent, they decided to name it ''Event Horizon'' after the point of no return surrounding black holes. The zone, once online never took off. It was briefly hosted on Can-Link before the hosting service imploded. After considering that the zone had only reached a maximum population of 4 players, the zone was abandoned and the group perused more rewarding games such as Infantry and Starcraft.

=== Dog Fight ===

Months later, Dr Brain revived the zone under the name ''Dog Fight'' with a new map. Again, nothing happened with the zone and it was closed.

=== Jeff's Zone ===

In order to experiment with [[Subgame2]] Dr Brain again hosted Dog Fight under the new name ''Jeff's Stupid Zone''. After some days of fiddling, Dr Brain finally figured out how to make Hypertunnels work. He remade the map and added some Hypertunnels around the very edge of the map. The zone's population doubled to a whole 6 players at peak times. Encouraged by this incredible population boost, more Hypertunnels were added and the zone was renamed to ''Jeff's Zone''.

=== Hosting, at last ===

Ever since the collapse of Can-Link, the zone had been hosted by Dr Brain on his cable connection. This lead to occasional downtime because of computer crashes and also to more lag than was preferable. SSDZ offered its services and the zone was moved.

=== Hyperspace ===

Dr Brain felt, now that the zone was picking up, that the name ''Jeff's Zone'' was no longer good enough. So, he started asking the player population about new name ideas. Someone suggested the name ''Hyperspeed'' and everyone agreed that it was a great name. Somehow, Dr Brain forgot the exact details of the name and changed the name to ''Hyperspace''. Only later did he realize that everyone had agreed to ''Hyperspeed'', but by then, it was too late to change.

=== Project 0 ===

This zone was created mainly for graphics testing but later on became "known" for a small heavily bot maintained arena called Warp2 (warpto joke). Many colorful graphics and anime girls (specifically catgirls) were featured here.

Average population was around eight and at max 14, not counting 6 bots (only 1 full time).

=== SSXH ===

The intermittent failures of SSDZ lead Dr Brain and picano2.0 to search for new hosting. SSXH under Delta_5 agreed to host the zone and a long period of prosperity for Hyperspace started.

=== SSND/SSDX ===

Eventually, SSXH decided to close down. A new host was needed and the SSDX network accepted Hyperspace. After a merger between SSDX and SSN, and several moves between servers on the SSN network, Hyperspace eventually settled down. Unfortunatly, the peace was not to last. Within weeks of quieting down, SSN closed down for no obvious reason.

=== SSI ===

Due to the collapse of SSN, Hyperspace was again hostless and had to be hosted by Dr Brain's less-than-perfect connection. Eventually, hosting was secured from SSI (run by 1stStrike and Argyle). Again, the zone flourished.

=== Getting SSC ===

Slowly, over time, the zone's regular population grew large enough to warrant inclusion on the SSC billing network. However, once the zone received SSC billing, the population went down to virtually zero. Something new had to be introduced or the zone would vanish into nothingness.

=== TWCore & AreaBot ===

As part of the SSI hosting package, Hyperspace developers were given access to the [[TWCore]] bot system (at the time, it was not public access). With this system, Nikon F5 and Dr Brain built a warping bot named AreaBot in the angelmass arena to help stimulate population. Eventually, this warping bot was extended to include a system to buy powerups. The system was again extended to include tracking of money and powerups across sessions using a MySQL database. The bot grew in complexity until eventually it housed a fully featured buy system and three discrete methods of warping. Once introduced into the public arena, the zone's population took off.

All was not well with the AreaBot, though. Because of the huge packet processing demands made on the TWCore system, a modified version of the TWCore was needed. The modified version was not as stable as the standard version, though, and reliability problems plagued the bot. The warping and buying parts of AreaBot were separated out into two bots to help alleviate some of the strain on the system. Mods were needed online 24/7 to restart the bots when they crashed. Obviously, this couldn't continue. The decision was made to move the zone to ASSS and hopefully solve the reliability problems of AreaBot.

=== ASSS ===

The port from Java based TWCore to C based ASSS was not easy, especially because there were only a few people with any experience in ASSS. Dr Brain was the programmer in charge of the porting. After a few weeks of stop and go, both a direct port of the buy system and a scaled back version of the warper were both ready to go.

The old subgame was shutdown and the new ASSS was started. Everything worked at first, but then disaster struck. The lag coma bug that would plague the zone for the next year had started its reign of terror. A lag coma is what happens when a player stops receiving reliable packets from the server. This means that a player can still fly around and shoot, but cannot change ship or see anyone else's messages. The only remedy for a lag comaed player was for them to exit and re-enter the zone. The bug seemed to only happen when there were ten or more players on the server, so the zone's former evening peak of 45 players quickly became an evening peak of 15, and slowly kept decreasing.

It was about this time that SSI's servers were upgraded from Microsoft Windows 2000 to Microsoft Windows 2003 Server. When this happened, the carefully compiled Windows version of ASSS would no longer run, and the zone was forced to close once more.

=== SSCX-A ===

Hearing of the trouble Hyperspace was in, hosting was offered from the people at SSCX who were in the process of setting up a new server running Linux, ASSS's native platform.

-add more

[[Category: Zones]]

Writing Modules for Hyperspace

2005-01-18T13:59:23Z

Dr Brain: Had the link backwards

== Getting Started ==

The first thing you should do is check with Dr Brain to make sure someone else isn't already making a similar module. The best way to contact him is in [[Hyperspace|SSCX-A Hyperspace]] via PM, ?message or with AIM/ICQ (check the Hyperspace news file for AIM name and ICQ number).

== General Info ==

In general, hard coding values is frowned upon. Please try to use the arena and global configs wherever possible. Put a sensible default into the '''GetInt''' so that not every config entry needs to be present for the module to work.

== Naming ==

Because of module naming conflicts, all official Hyperspace related modules are prefixed with hs_. So, for example, a kill spree module becomes hs_spree. This is not required for module submissions. You are free to name your module whatever you wish.

== Style ==

There is a Hyperspace standard style for formatting code, but it is completely optional. You should make your interface headers easy to read, though.

Here is an example of the Hyperspace official style:

''hs_twowords.h'':
<pre>
#ifndef HS_TWOWORDS_H
#define HS_TWOWORDS_H

#define I_HS_TWOWORDS "hs_twowords-1"

typedef struct Ihstwowords
{
INTERFACE_HEAD_DECL

int (*interfaceFunction)(Player *p);
} Ihstwowords;

#endif //HS_TWOWORDS_H
</pre>

''hs_twowords.c'':
<pre>
#include <string.h> //optional. others added as needed

#include "asss.h"
#include "hscore.h"
#include "hs_twowords.h"

//modules
local Imodman *mm;
local Ilogman *lm;
local Ichat *chat;
local Iconfig *cfg;
local Icmdman *cmd;
local Iplayerdata *pd;

//interface prototypes
local int interfaceFunction(Player *p);

local helptext_t twoWordsHelp =
"Targets: player\n"
"Args: none\n"
"Who knows? This is just a template file.\n";

local void twoWordsCommand(const char *command, const char *params, Player *p, const Target *target)
{
if (target->type == T_PLAYER) //private command
{
Player *t = target->u.p;

//do something
}
else //not private
{
chat->SendMessage(p, "You must target a player.");
}
}

local int interfaceFunction(Player *p)
{
if (something) //space between if and ()
{
//do something
}
}

local Ihstwowords interface =
{
INTERFACE_HEAD_INIT(I_HS_TWOWORDS, "hs_twowords")
interfaceFunction
};

EXPORT int MM_hs_twowords(int action, Imodman *_mm, Arena *arena)
{
if (action == MM_LOAD)
{
mm = _mm;

lm = mm->GetInterface(I_LOGMAN, ALLARENAS);
chat = mm->GetInterface(I_CHAT, ALLARENAS);
cfg = mm->GetInterface(I_CONFIG, ALLARENAS);
cmd = mm->GetInterface(I_CMDMAN, ALLARENAS);
pd = mm->GetInterface(I_PLAYERDATA, ALLARENAS);

if (!lm || !chat || !cfg || !cmd || !pd)
{
mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(cfg);
mm->ReleaseInterface(cmd);
mm->ReleaseInterface(pd);

return MM_FAIL;
}

mm->RegInterface(&interface, ALLARENAS);

cmd->AddCommand("twowords", twoWordsCommand, ALLARENAS, twoWordsHelp);

return MM_OK;
}
else if (action == MM_UNLOAD)
{
if (mm->UnregInterface(&interface, ALLARENAS))
{
return MM_FAIL;
}

cmd->RemoveCommand("twowords", twoWordsCommand, ALLARENAS);

mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(cfg);
mm->ReleaseInterface(cmd);
mm->ReleaseInterface(pd);

return MM_OK;
}
return MM_FAIL;
}
</pre>

== Required Files ==

Downloadable versions of the files can be found [http://hyperspace.sscentral.com/hscore/ here].

Here is ''hscore.h'':
<pre>
#include "hscore_types.h"

#include "hscore_money.h"
#include "hscore_items.h"
</pre>

Here is ''hscore_types.h'':
<pre>
#ifndef HSCORE_TYPES_H
#define HSCORE_TYPES_H

typedef enum EventAction
{
//removes event->data amount of the items from the ship's inventory
ACTION_REMOVE_ITEM = 0,

//removes event->data amount of the item's ammo type from inventory
ACTION_REMOVE_ITEM_AMMO,

//sends prize #event->data to the player
ACTION_PRIZE,

//sets the item's inventory data to event->data. This is useful with
//the "purchace" event.
ACTION_SET_INVENTORY_DATA,

//does a ++ on inventory data.
ACTION_INCREMENT_INVENTORY_DATA,

//does a -- on inventory data. A "datazero" event may be generated as a result.
ACTION_DECREMENT_INVENTORY_DATA,

//Specs the player.
ACTION_SPEC,

//sends a shipreset packet and reprizes all items (antideath, really)
ACTION_SHIP_RESET

//we need a lot more
} EventAction;

typedef struct Event
{
char event[16]; //something like "death" or "datazero"
EventAction action;

int data; //action dependent

char message[200]; //if == to "" then nothing will be sent.
} Event;

typedef struct Property
{
char name[16];
int value;
} Property;

typedef struct ItemType
{
char name[32];
int max; //maximum total of this item type on a ship before ?buy denies purchace

int id; //MySQL use only
} ItemType;

typedef struct Item
{
char name[16];
char shortDesc[32]; //displayed inline in the ?buy menu
char longDesc[200]; //displayed as part of ?iteminfo
int buyPrice;
int sellPrice;

int expRequired; //requirement to own

int shipsAllowed; //bit positions represent each ship. bit 0 = warbird.

LinkedList propertyList;

LinkedList eventList;

ItemType *type1, *type2;
int typeDelta1, typeDelta2;

int max;

//if changes to this item should be delayed until a complete save (like on exit).
//This is a necessity when dealing with ammo. We don't want to update MySQL every
//time a gun is fired.
int delayStatusWrite;

struct Item *ammo; //can be NULL, only for use by events.
int ammoID; //used for post processing ONLY

int id; //MySQL use only
} Item;

typedef struct InventoryEntry
{
Item *item;
int count;

int data; //persistent int for use by the event system.
} InventoryEntry;

typedef struct ShipHull
{
LinkedList inventoryEntryList;

//NOTE: no need for ship #, as it's defined by the array index (when loaded by hscore_database)

//if we compile a hashmap of properties, it can go in here.

int id; //MySQL use only
} ShipHull;

typedef struct Category
{
char name[32]; //displayed on ?buy
char description[64]; //displayed inline on the ?buy menu

LinkedList itemList; //a list of member items that are displayed

int id; //mysql use
} Category;

typedef struct Store
{
char name[32]; //displayed in ?buysell location errors
char description[200]; //displayed in ?storeinfo
char region[16]; //region that defines the store

LinkedList itemList; //a list of items that can be purchaced here

int id; //mysql use
} Store;

#endif //HSCORE_TYPES_H
</pre>

Here is the ''hscore_money.h'':

<pre>
#ifndef HSCORE_MONEY_H
#define HSCORE_MONEY_H

#define I_HSCORE_MONEY "hscore_money-1"

typedef enum MoneyType
{
//for /?give
MONEY_TYPE_GIVE = 0,

//for /?grant
MONEY_TYPE_GRANT,

//for ?buy and ?sell
MONEY_TYPE_BUYSELL,

//for money from kills
MONEY_TYPE_KILL,

//for money from flag games
MONEY_TYPE_FLAG,

//for money from soccer games
MONEY_TYPE_BALL,

//for money from module driven events
MONEY_TYPE_EVENT
} MoneyType;

#define MONEY_TYPE_COUNT 7

typedef struct Ihscoremoney
{
INTERFACE_HEAD_DECL

void (*giveMoney)(Player *p, int amount, MoneyType type);
void (*setMoney)(Player *p, int amount, MoneyType type); //beware. know what you're doing

int (*getMoney)(Player *p);
int (*getMoneyType)(Player *p, MoneyType type); //used only for /?money -d

void (*giveExp)(Player *p, int amount);
void (*setExp)(Player *p, int amount); //beware. know what you're doing

int (*getExp)(Player *p);
} Ihscoremoney;

#endif //HSCORE_MONEY_H
</pre>

Here is ''hscore_item.h'':
<pre>
#ifndef HSCORE_ITEMS_H
#define HSCORE_ITEMS_H

#define I_HSCORE_ITEMS "hscore_items-3"

typedef struct Ihscoreitems
{
INTERFACE_HEAD_DECL

int (*getItemCount)(Player *p, Item *item, int ship);
void (*addItem)(Player *p, Item *item, int ship, int amount);

Item * (*getItemByName)(const char *name, Arena *arena);

int (*getPropertySum)(Player *p, int ship, const char *prop); //properties ARE case sensitive

void (*triggerEvent)(Player *p, int ship, const char *event);
void (*triggerEventOnItem)(Player *p, Item *item, int ship, const char *event);

int (*getFreeItemTypeSpots)(Player *p, ItemType *type, int ship);

//more required, i'm sure
} Ihscoreitems;

#endif //HSCORE_ITEMS_H
</pre>

== Optional Files ==

Here is ''hscore_moneystub.c'':
<pre>
#include "asss.h"
#include "hscore.h"

//modules
local Imodman *mm;
local Ilogman *lm;
local Ichat *chat;
local Iplayerdata *pd;

//interface prototypes
local void giveMoney(Player *p, int amount, MoneyType type);
local void setMoney(Player *p, int amount, MoneyType type);
local int getMoney(Player *p);
local int getMoneyType(Player *p, MoneyType type);
local void giveExp(Player *p, int amount);
local void setExp(Player *p, int amount);
local int getExp(Player *p);

local void giveMoney(Player *p, int amount, MoneyType type)
{
chat->SendMessage(p, "hscore_moneystub.c: giveMoney(%i) called.", amount);
}

local void setMoney(Player *p, int amount, MoneyType type)
{
chat->SendMessage(p, "setMoney should not be used.");
}

local int getMoney(Player *p)
{
return 0; //change for testing
}

local int getMoneyType(Player *p, MoneyType type)
{
chat->SendMessage(p, "getMoneyType should not be used.");
return 0;
}

local void giveExp(Player *p, int amount)
{
chat->SendMessage(p, "hscore_moneystub.c: giveExp(%i) called.", amount);
}

local void setExp(Player *p, int amount)
{
chat->SendMessage(p, "setExp should not be used.");
}

local int getExp(Player *p)
{
return 0; //change for testing
}

local Ihscoremoney interface =
{
INTERFACE_HEAD_INIT(I_HSCORE_MONEY, "hscore_moneystub")
giveMoney, setMoney, getMoney, getMoneyType,
giveExp, setExp, getExp,
};

EXPORT int MM_hscore_moneystub(int action, Imodman *_mm, Arena *arena)
{
if (action == MM_LOAD)
{
mm = _mm;

lm = mm->GetInterface(I_LOGMAN, ALLARENAS);
chat = mm->GetInterface(I_CHAT, ALLARENAS);
pd = mm->GetInterface(I_PLAYERDATA, ALLARENAS);

if (!lm || !chat || !pd)
{
mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(pd);

return MM_FAIL;
}

mm->RegInterface(&interface, ALLARENAS);

return MM_OK;
}
else if (action == MM_UNLOAD)
{
if (mm->UnregInterface(&interface, ALLARENAS))
{
return MM_FAIL;
}

mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(pd);

return MM_OK;
}
return MM_FAIL;
}
</pre>

Here is ''hscore_itemsstub.c'':
<pre>
#include "asss.h"
#include "hscore.h"

//modules
local Imodman *mm;
local Ilogman *lm;
local Ichat *chat;
local Iplayerdata *pd;

//interface prototypes
local int getItemCount(Player *p, Item *item, int ship);
local void addItem(Player *p, Item *item, int ship, int amount);
local Item * getItemByName(const char *name, Arena *arena);
local int getPropertySum(Player *p, int ship, const char *prop);
local void triggerEvent(Player *p, int ship, const char *event);
local void triggerEventOnItem(Player *p, Item *item, int ship, const char *event);
local int getFreeItemTypeSpots(Player *p, ItemType *type, int ship);

local int getItemCount(Player *p, Item *item, int ship)
{
chat->SendMessage(p, "getItemCount should not be used by non-core modules!");

return 0;
}

local void addItem(Player *p, Item *item, int ship, int amount)
{
chat->SendMessage(p, "addItem should not be used by non-core modules!");
}

local Item * getItemByName(const char *name, Arena *arena)
{
chat->SendArenaMessage(arena, "Tried to getItemByName(%s)", name);

return NULL;
}

local int getPropertySum(Player *p, int ship, const char *propString)
{
if (propString == NULL)
{
lm->LogP(L_ERROR, "hscore_itemsstub", p, "asked to get props for NULL string.");
return 0;
}

if (ship < 0 || 7 < ship)
{
lm->LogP(L_ERROR, "hscore_itemsstub", p, "asked to get props on ship %i", ship);
return 0;
}

//change this value for testing
return 0;
}

local void triggerEvent(Player *p, int ship, const char *event)
{
if (ship < 0 || 7 < ship)
{
lm->LogP(L_ERROR, "hscore_itemsstub", p, "asked to get props on ship %i", ship);
}

if (event == NULL)
{
lm->LogP(L_ERROR, "hscore_itemsstub", p, "asked to trigger event with NULL string.");
return;
}

chat->SendMessage(p, "triggered event %s!", event);
}

local void triggerEventOnItem(Player *p, Item *item, int ship, const char *event)
{
chat->SendMessage(p, "triggerEventOnItem should not be used by non-core modules!");
}

local int getFreeItemTypeSpots(Player *p, ItemType *type, int ship)
{
chat->SendMessage(p, "getFreeItemTypeSpots should not be used by non-core modules!");
return 0;
}

local Ihscoreitems interface =
{
INTERFACE_HEAD_INIT(I_HSCORE_ITEMS, "hscore_itemsstub")
getItemCount, addItem, getItemByName, getPropertySum,
triggerEvent, triggerEventOnItem, getFreeItemTypeSpots,
};

EXPORT int MM_hscore_itemsstub(int action, Imodman *_mm, Arena *arena)
{
if (action == MM_LOAD)
{
mm = _mm;

lm = mm->GetInterface(I_LOGMAN, ALLARENAS);
chat = mm->GetInterface(I_CHAT, ALLARENAS);
pd = mm->GetInterface(I_PLAYERDATA, ALLARENAS);

if (!lm || !chat || !pd)
{
mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(pd);

return MM_FAIL;
}

mm->RegInterface(&interface, ALLARENAS);

return MM_OK;
}
else if (action == MM_UNLOAD)
{
if (mm->UnregInterface(&interface, ALLARENAS))
{
return MM_FAIL;
}

mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(pd);

return MM_OK;
}
return MM_FAIL;
}
</pre>

== Money and Experience ==

Money and experience points (aka exp) are what make the Hyperspace world go 'round. Nearly every Hyperspace module has some dealings with money/exp transactions of some kind.

=== Giving exp ===

<pre>
money->giveExp(p, 10); //gives player p 10 exp
</pre>

=== Giving money ===

The first thing to decide is which money type to give. This is mainly used for tracking purposes. If in doubt, choose '''MONEY_TYPE_EVENT'''.

*'''MONEY_TYPE_GIVE''' is for money moving from one player to another.
*'''MONEY_TYPE_GRANT''' is for money coming from a grant command
*'''MONEY_TYPE_BUYSELL''' is for ?buying and ?selling.
*'''MONEY_TYPE_KILL''' is for money gained from kills.
*'''MONEY_TYPE_FLAG''' is for money earned from winning flag games or other flag rewards.
*'''MONEY_TYPE_BALL''' is for money received from goals.
*'''MONEY_TYPE_EVENT''' is for subarena events.

Then you can simply call:
<pre>
money->giveMoney(p, 1000, MONEY_TYPE_EVENT); //gives player p $1000
</pre>

== Using Items ==

Items are the most important part of Hyperspace after money and exp. There are two parts of items that addon modules will use. These are checking for properties and calling events. While module writers cannot directly create items, they can request item modification/addition from subarena owners.

=== Item properties ===

Most items define properties that are used to change the player's ship. Properties are totalled for each ship and are checked per ship rather than per item. Most properties are related to the spawning module. However, any item can define custom properties. For example, if you have a subway system, a module could check if a player has at least one subway token property. You can check if the property sum on the player's current ship for "subway" is greater than 0, and if it is, let them ride.

<pre>
item->getPropertySum(p, p->p_ship, "someproperty"); //Beware of spectators.
</pre>

=== Item events ===

Items define actions that happen on certain events. Any module can trigger an event. Some modules, for example, have actions on the ''death'' event. Triggering an event is as simple as making a function call to the '''hscore_item''' module. If no items have actions on the called event, nothing will happen (so make sure you don't typo the event name). Following on the previous example, when a player rides the subway, then you can call the "ridesubway" event. The Subway Token items can define an action of self removal on that event.

<pre>
item->triggerEvent(p, p->p_ship, "someevent"); //Beware of spectators.
</pre>

== Submission ==

Once your module is working properly and seems to have no bugs, then you can submit the source to Dr Brain or MichaelG for a source check. Once that's completed, the module will be compiled for the Hyperspace server and installed.

[[Category: Module]]
[[Category: Tutorial]]

Writing Modules for Hyperspace

2005-01-18T13:58:59Z

Dr Brain: Added stub files and rearranged the files

== Getting Started ==

The first thing you should do is check with Dr Brain to make sure someone else isn't already making a similar module. The best way to contact him is in [[SSCX-A Hyperspace|Hyperspace]] via PM, ?message or with AIM/ICQ (check the Hyperspace news file for AIM name and ICQ number).

== General Info ==

In general, hard coding values is frowned upon. Please try to use the arena and global configs wherever possible. Put a sensible default into the '''GetInt''' so that not every config entry needs to be present for the module to work.

== Naming ==

Because of module naming conflicts, all official Hyperspace related modules are prefixed with hs_. So, for example, a kill spree module becomes hs_spree. This is not required for module submissions. You are free to name your module whatever you wish.

== Style ==

There is a Hyperspace standard style for formatting code, but it is completely optional. You should make your interface headers easy to read, though.

Here is an example of the Hyperspace official style:

''hs_twowords.h'':
<pre>
#ifndef HS_TWOWORDS_H
#define HS_TWOWORDS_H

#define I_HS_TWOWORDS "hs_twowords-1"

typedef struct Ihstwowords
{
INTERFACE_HEAD_DECL

int (*interfaceFunction)(Player *p);
} Ihstwowords;

#endif //HS_TWOWORDS_H
</pre>

''hs_twowords.c'':
<pre>
#include <string.h> //optional. others added as needed

#include "asss.h"
#include "hscore.h"
#include "hs_twowords.h"

//modules
local Imodman *mm;
local Ilogman *lm;
local Ichat *chat;
local Iconfig *cfg;
local Icmdman *cmd;
local Iplayerdata *pd;

//interface prototypes
local int interfaceFunction(Player *p);

local helptext_t twoWordsHelp =
"Targets: player\n"
"Args: none\n"
"Who knows? This is just a template file.\n";

local void twoWordsCommand(const char *command, const char *params, Player *p, const Target *target)
{
if (target->type == T_PLAYER) //private command
{
Player *t = target->u.p;

//do something
}
else //not private
{
chat->SendMessage(p, "You must target a player.");
}
}

local int interfaceFunction(Player *p)
{
if (something) //space between if and ()
{
//do something
}
}

local Ihstwowords interface =
{
INTERFACE_HEAD_INIT(I_HS_TWOWORDS, "hs_twowords")
interfaceFunction
};

EXPORT int MM_hs_twowords(int action, Imodman *_mm, Arena *arena)
{
if (action == MM_LOAD)
{
mm = _mm;

lm = mm->GetInterface(I_LOGMAN, ALLARENAS);
chat = mm->GetInterface(I_CHAT, ALLARENAS);
cfg = mm->GetInterface(I_CONFIG, ALLARENAS);
cmd = mm->GetInterface(I_CMDMAN, ALLARENAS);
pd = mm->GetInterface(I_PLAYERDATA, ALLARENAS);

if (!lm || !chat || !cfg || !cmd || !pd)
{
mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(cfg);
mm->ReleaseInterface(cmd);
mm->ReleaseInterface(pd);

return MM_FAIL;
}

mm->RegInterface(&interface, ALLARENAS);

cmd->AddCommand("twowords", twoWordsCommand, ALLARENAS, twoWordsHelp);

return MM_OK;
}
else if (action == MM_UNLOAD)
{
if (mm->UnregInterface(&interface, ALLARENAS))
{
return MM_FAIL;
}

cmd->RemoveCommand("twowords", twoWordsCommand, ALLARENAS);

mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(cfg);
mm->ReleaseInterface(cmd);
mm->ReleaseInterface(pd);

return MM_OK;
}
return MM_FAIL;
}
</pre>

== Required Files ==

Downloadable versions of the files can be found [http://hyperspace.sscentral.com/hscore/ here].

Here is ''hscore.h'':
<pre>
#include "hscore_types.h"

#include "hscore_money.h"
#include "hscore_items.h"
</pre>

Here is ''hscore_types.h'':
<pre>
#ifndef HSCORE_TYPES_H
#define HSCORE_TYPES_H

typedef enum EventAction
{
//removes event->data amount of the items from the ship's inventory
ACTION_REMOVE_ITEM = 0,

//removes event->data amount of the item's ammo type from inventory
ACTION_REMOVE_ITEM_AMMO,

//sends prize #event->data to the player
ACTION_PRIZE,

//sets the item's inventory data to event->data. This is useful with
//the "purchace" event.
ACTION_SET_INVENTORY_DATA,

//does a ++ on inventory data.
ACTION_INCREMENT_INVENTORY_DATA,

//does a -- on inventory data. A "datazero" event may be generated as a result.
ACTION_DECREMENT_INVENTORY_DATA,

//Specs the player.
ACTION_SPEC,

//sends a shipreset packet and reprizes all items (antideath, really)
ACTION_SHIP_RESET

//we need a lot more
} EventAction;

typedef struct Event
{
char event[16]; //something like "death" or "datazero"
EventAction action;

int data; //action dependent

char message[200]; //if == to "" then nothing will be sent.
} Event;

typedef struct Property
{
char name[16];
int value;
} Property;

typedef struct ItemType
{
char name[32];
int max; //maximum total of this item type on a ship before ?buy denies purchace

int id; //MySQL use only
} ItemType;

typedef struct Item
{
char name[16];
char shortDesc[32]; //displayed inline in the ?buy menu
char longDesc[200]; //displayed as part of ?iteminfo
int buyPrice;
int sellPrice;

int expRequired; //requirement to own

int shipsAllowed; //bit positions represent each ship. bit 0 = warbird.

LinkedList propertyList;

LinkedList eventList;

ItemType *type1, *type2;
int typeDelta1, typeDelta2;

int max;

//if changes to this item should be delayed until a complete save (like on exit).
//This is a necessity when dealing with ammo. We don't want to update MySQL every
//time a gun is fired.
int delayStatusWrite;

struct Item *ammo; //can be NULL, only for use by events.
int ammoID; //used for post processing ONLY

int id; //MySQL use only
} Item;

typedef struct InventoryEntry
{
Item *item;
int count;

int data; //persistent int for use by the event system.
} InventoryEntry;

typedef struct ShipHull
{
LinkedList inventoryEntryList;

//NOTE: no need for ship #, as it's defined by the array index (when loaded by hscore_database)

//if we compile a hashmap of properties, it can go in here.

int id; //MySQL use only
} ShipHull;

typedef struct Category
{
char name[32]; //displayed on ?buy
char description[64]; //displayed inline on the ?buy menu

LinkedList itemList; //a list of member items that are displayed

int id; //mysql use
} Category;

typedef struct Store
{
char name[32]; //displayed in ?buysell location errors
char description[200]; //displayed in ?storeinfo
char region[16]; //region that defines the store

LinkedList itemList; //a list of items that can be purchaced here

int id; //mysql use
} Store;

#endif //HSCORE_TYPES_H
</pre>

Here is the ''hscore_money.h'':

<pre>
#ifndef HSCORE_MONEY_H
#define HSCORE_MONEY_H

#define I_HSCORE_MONEY "hscore_money-1"

typedef enum MoneyType
{
//for /?give
MONEY_TYPE_GIVE = 0,

//for /?grant
MONEY_TYPE_GRANT,

//for ?buy and ?sell
MONEY_TYPE_BUYSELL,

//for money from kills
MONEY_TYPE_KILL,

//for money from flag games
MONEY_TYPE_FLAG,

//for money from soccer games
MONEY_TYPE_BALL,

//for money from module driven events
MONEY_TYPE_EVENT
} MoneyType;

#define MONEY_TYPE_COUNT 7

typedef struct Ihscoremoney
{
INTERFACE_HEAD_DECL

void (*giveMoney)(Player *p, int amount, MoneyType type);
void (*setMoney)(Player *p, int amount, MoneyType type); //beware. know what you're doing

int (*getMoney)(Player *p);
int (*getMoneyType)(Player *p, MoneyType type); //used only for /?money -d

void (*giveExp)(Player *p, int amount);
void (*setExp)(Player *p, int amount); //beware. know what you're doing

int (*getExp)(Player *p);
} Ihscoremoney;

#endif //HSCORE_MONEY_H
</pre>

Here is ''hscore_item.h'':
<pre>
#ifndef HSCORE_ITEMS_H
#define HSCORE_ITEMS_H

#define I_HSCORE_ITEMS "hscore_items-3"

typedef struct Ihscoreitems
{
INTERFACE_HEAD_DECL

int (*getItemCount)(Player *p, Item *item, int ship);
void (*addItem)(Player *p, Item *item, int ship, int amount);

Item * (*getItemByName)(const char *name, Arena *arena);

int (*getPropertySum)(Player *p, int ship, const char *prop); //properties ARE case sensitive

void (*triggerEvent)(Player *p, int ship, const char *event);
void (*triggerEventOnItem)(Player *p, Item *item, int ship, const char *event);

int (*getFreeItemTypeSpots)(Player *p, ItemType *type, int ship);

//more required, i'm sure
} Ihscoreitems;

#endif //HSCORE_ITEMS_H
</pre>

== Optional Files ==

Here is ''hscore_moneystub.c'':
<pre>
#include "asss.h"
#include "hscore.h"

//modules
local Imodman *mm;
local Ilogman *lm;
local Ichat *chat;
local Iplayerdata *pd;

//interface prototypes
local void giveMoney(Player *p, int amount, MoneyType type);
local void setMoney(Player *p, int amount, MoneyType type);
local int getMoney(Player *p);
local int getMoneyType(Player *p, MoneyType type);
local void giveExp(Player *p, int amount);
local void setExp(Player *p, int amount);
local int getExp(Player *p);

local void giveMoney(Player *p, int amount, MoneyType type)
{
chat->SendMessage(p, "hscore_moneystub.c: giveMoney(%i) called.", amount);
}

local void setMoney(Player *p, int amount, MoneyType type)
{
chat->SendMessage(p, "setMoney should not be used.");
}

local int getMoney(Player *p)
{
return 0; //change for testing
}

local int getMoneyType(Player *p, MoneyType type)
{
chat->SendMessage(p, "getMoneyType should not be used.");
return 0;
}

local void giveExp(Player *p, int amount)
{
chat->SendMessage(p, "hscore_moneystub.c: giveExp(%i) called.", amount);
}

local void setExp(Player *p, int amount)
{
chat->SendMessage(p, "setExp should not be used.");
}

local int getExp(Player *p)
{
return 0; //change for testing
}

local Ihscoremoney interface =
{
INTERFACE_HEAD_INIT(I_HSCORE_MONEY, "hscore_moneystub")
giveMoney, setMoney, getMoney, getMoneyType,
giveExp, setExp, getExp,
};

EXPORT int MM_hscore_moneystub(int action, Imodman *_mm, Arena *arena)
{
if (action == MM_LOAD)
{
mm = _mm;

lm = mm->GetInterface(I_LOGMAN, ALLARENAS);
chat = mm->GetInterface(I_CHAT, ALLARENAS);
pd = mm->GetInterface(I_PLAYERDATA, ALLARENAS);

if (!lm || !chat || !pd)
{
mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(pd);

return MM_FAIL;
}

mm->RegInterface(&interface, ALLARENAS);

return MM_OK;
}
else if (action == MM_UNLOAD)
{
if (mm->UnregInterface(&interface, ALLARENAS))
{
return MM_FAIL;
}

mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(pd);

return MM_OK;
}
return MM_FAIL;
}
</pre>

Here is ''hscore_itemsstub.c'':
<pre>
#include "asss.h"
#include "hscore.h"

//modules
local Imodman *mm;
local Ilogman *lm;
local Ichat *chat;
local Iplayerdata *pd;

//interface prototypes
local int getItemCount(Player *p, Item *item, int ship);
local void addItem(Player *p, Item *item, int ship, int amount);
local Item * getItemByName(const char *name, Arena *arena);
local int getPropertySum(Player *p, int ship, const char *prop);
local void triggerEvent(Player *p, int ship, const char *event);
local void triggerEventOnItem(Player *p, Item *item, int ship, const char *event);
local int getFreeItemTypeSpots(Player *p, ItemType *type, int ship);

local int getItemCount(Player *p, Item *item, int ship)
{
chat->SendMessage(p, "getItemCount should not be used by non-core modules!");

return 0;
}

local void addItem(Player *p, Item *item, int ship, int amount)
{
chat->SendMessage(p, "addItem should not be used by non-core modules!");
}

local Item * getItemByName(const char *name, Arena *arena)
{
chat->SendArenaMessage(arena, "Tried to getItemByName(%s)", name);

return NULL;
}

local int getPropertySum(Player *p, int ship, const char *propString)
{
if (propString == NULL)
{
lm->LogP(L_ERROR, "hscore_itemsstub", p, "asked to get props for NULL string.");
return 0;
}

if (ship < 0 || 7 < ship)
{
lm->LogP(L_ERROR, "hscore_itemsstub", p, "asked to get props on ship %i", ship);
return 0;
}

//change this value for testing
return 0;
}

local void triggerEvent(Player *p, int ship, const char *event)
{
if (ship < 0 || 7 < ship)
{
lm->LogP(L_ERROR, "hscore_itemsstub", p, "asked to get props on ship %i", ship);
}

if (event == NULL)
{
lm->LogP(L_ERROR, "hscore_itemsstub", p, "asked to trigger event with NULL string.");
return;
}

chat->SendMessage(p, "triggered event %s!", event);
}

local void triggerEventOnItem(Player *p, Item *item, int ship, const char *event)
{
chat->SendMessage(p, "triggerEventOnItem should not be used by non-core modules!");
}

local int getFreeItemTypeSpots(Player *p, ItemType *type, int ship)
{
chat->SendMessage(p, "getFreeItemTypeSpots should not be used by non-core modules!");
return 0;
}

local Ihscoreitems interface =
{
INTERFACE_HEAD_INIT(I_HSCORE_ITEMS, "hscore_itemsstub")
getItemCount, addItem, getItemByName, getPropertySum,
triggerEvent, triggerEventOnItem, getFreeItemTypeSpots,
};

EXPORT int MM_hscore_itemsstub(int action, Imodman *_mm, Arena *arena)
{
if (action == MM_LOAD)
{
mm = _mm;

lm = mm->GetInterface(I_LOGMAN, ALLARENAS);
chat = mm->GetInterface(I_CHAT, ALLARENAS);
pd = mm->GetInterface(I_PLAYERDATA, ALLARENAS);

if (!lm || !chat || !pd)
{
mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(pd);

return MM_FAIL;
}

mm->RegInterface(&interface, ALLARENAS);

return MM_OK;
}
else if (action == MM_UNLOAD)
{
if (mm->UnregInterface(&interface, ALLARENAS))
{
return MM_FAIL;
}

mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(pd);

return MM_OK;
}
return MM_FAIL;
}
</pre>

== Money and Experience ==

Money and experience points (aka exp) are what make the Hyperspace world go 'round. Nearly every Hyperspace module has some dealings with money/exp transactions of some kind.

=== Giving exp ===

<pre>
money->giveExp(p, 10); //gives player p 10 exp
</pre>

=== Giving money ===

The first thing to decide is which money type to give. This is mainly used for tracking purposes. If in doubt, choose '''MONEY_TYPE_EVENT'''.

*'''MONEY_TYPE_GIVE''' is for money moving from one player to another.
*'''MONEY_TYPE_GRANT''' is for money coming from a grant command
*'''MONEY_TYPE_BUYSELL''' is for ?buying and ?selling.
*'''MONEY_TYPE_KILL''' is for money gained from kills.
*'''MONEY_TYPE_FLAG''' is for money earned from winning flag games or other flag rewards.
*'''MONEY_TYPE_BALL''' is for money received from goals.
*'''MONEY_TYPE_EVENT''' is for subarena events.

Then you can simply call:
<pre>
money->giveMoney(p, 1000, MONEY_TYPE_EVENT); //gives player p $1000
</pre>

== Using Items ==

Items are the most important part of Hyperspace after money and exp. There are two parts of items that addon modules will use. These are checking for properties and calling events. While module writers cannot directly create items, they can request item modification/addition from subarena owners.

=== Item properties ===

Most items define properties that are used to change the player's ship. Properties are totalled for each ship and are checked per ship rather than per item. Most properties are related to the spawning module. However, any item can define custom properties. For example, if you have a subway system, a module could check if a player has at least one subway token property. You can check if the property sum on the player's current ship for "subway" is greater than 0, and if it is, let them ride.

<pre>
item->getPropertySum(p, p->p_ship, "someproperty"); //Beware of spectators.
</pre>

=== Item events ===

Items define actions that happen on certain events. Any module can trigger an event. Some modules, for example, have actions on the ''death'' event. Triggering an event is as simple as making a function call to the '''hscore_item''' module. If no items have actions on the called event, nothing will happen (so make sure you don't typo the event name). Following on the previous example, when a player rides the subway, then you can call the "ridesubway" event. The Subway Token items can define an action of self removal on that event.

<pre>
item->triggerEvent(p, p->p_ship, "someevent"); //Beware of spectators.
</pre>

== Submission ==

Once your module is working properly and seems to have no bugs, then you can submit the source to Dr Brain or MichaelG for a source check. Once that's completed, the module will be compiled for the Hyperspace server and installed.

[[Category: Module]]
[[Category: Tutorial]]

Talk:BanG

2005-01-15T14:23:25Z

Dr Brain:

[[User:Smong|Smong]]: This page shows how to bypass. Reword it and clean the wiki log?

How about putting a copy of the BanG command listing here instead?

Hyperspace

2005-01-14T02:41:35Z

Dr Brain: /* SSXH */ spelling fix

SSCX-A Hyperspace was one of the first zones to adopt [[ASSS]].

== Gameplay ==

== Staff ==

<table border=0 frame=void rules=cols width=50%>
<tr>
<td align=center colspan=3><h3>Sysops</h3></td>
</tr>
<tr>
<td align=center>[[User:Dr Brain|Dr Brain]]</td>
<td align=center>Picano</td>
</tr>
</table>

<table border=0 frame=void rules=cols width=50%>
<tr>
<td align=center colspan=3><h3>Smods</h3></td>
</tr>
<tr>
<td align=center>Nerusai</td>
</tr>
</table>

<table border=0 frame=void rules=cols width=50%>
<tr>
<td align=center colspan=4><h3>Moderators</h3></td>
</tr>
<tr>
<td align=center>D1st0rt</td>
<td align=center>Coenny</td>
<td align=center>Quigybobo</td>
<td align=center>Bomook</td>
</tr>
<tr>
<td align=center>Wargh</td>
<td align=center>FunkmastaD</td>
<td align=center>[[User:Nikegurl|nikegurl]]</td>
<td align=center>Lanvalk</td>
</tr>
</table>

== History ==

=== Event Horizon ===

Hyperspace started life as a LAN zone played by a small group of friends, Dr Brain among them. They eventually decided to put it online to try and get more players in it. Having something of a scientific bent, they decided to name it ''Event Horizon'' after the point of no return surrounding black holes. The zone, once online never took off. It was briefly hosted on Can-Link before the hosting service imploded. After considering that the zone had only reached a maximum population of 4 players, the zone was abandoned and the group persued more rewarding games such as Infantry and Starcraft.

=== Dog Fight ===

Months later, Dr Brain revived the zone under the name ''Dog Fight'' with a new map. Again, nothing happened with the zone and it was closed.

=== Jeff's Zone ===

In order to experiment with [[Subgame2]] Dr Brain again hosted Dog Fight under the new name ''Jeff's Stupid Zone''. After some days of fiddling, Dr Brain finally figured out how to make Hypertunnels work. He remade the map and added some Hypertunnels around the very edge of the map. The zone's population doubled to a whole 6 players at peak times. Encouraged by this incredible population boost, more hypertunnels were added and the zone was renamed to ''Jeff's Zone''.

=== Hosting, at last ===

Ever since the collapse of Can-Link, the zone had been hosted by Dr Brain on his cable connection. This lead to occasional downtime because of computer crashes and also to more lag than was preferable. SSDZ offered its services and the zone was moved.

=== Hyperspace ===

Dr Brain felt, now that the zone was picking up, that the name ''Jeff's Zone'' was no longer good enough. So, he started asking the player population about new name ideas. Someone suggested the name ''Hyperspeed'' and everyone agreed that it was a great name. Somehow, Dr Brain forgot the exact details of the name and changed the name to ''Hyperspace''. Only later did he realize that everyone had agreed to ''Hyperspeed'', but by then, it was too late to change.

=== Project 0 ===

This zone was created mainly for graphics testing but later on became "known" for a small heavily bot maintained arena called Warp2 (warpto joke). Many colorful graphics and anime girls (specifically catgirls) were featured here.

Average population was around eight and at max 14, not counting 6 bots (only 1 full time).

=== SSXH ===

The intermittent failures of SSDZ lead Dr Brain and picano2.0 to search for new hosting. SSXH under Delta_5 agreed to host the zone and a long period of prosperity for Hyperspace started.

=== SSND/SSDX ===

Eventually, SSXH decided to close down. A new host was needed and the SSDX network accepted Hyperspace. After a merger between SSDX and SSN, and several moves between servers on the SSN network, Hyperspace eventually settled down. Unfortuantly, the peace was not to last. Within weeks of quieting down, SSN closed down for no obvious reason.

=== SSI ===

Due to the collapse of SSN, Hyperspace was again hostless and had to be hosted by Dr Brain's less-than-perfect connection. Eventually, hosting was secured from SSI (run by 1stStrike and Argyle). Again, the zone flourished.

=== TWCore & AreaBot ===

As part of the SSI hosting package, Hyperspace developers were given access to the [[TWCore]] bot system (at the time, it was not public access). Everything was great for a while with small populations, but changes were needed to support the growing population. Initially, all kills gave 50 'HS Bucks'. This was changed to an earnings formula by [[User:D1st0rt|D1st0rt]] which was roughly 1+(killed bty / killer bty) * 50. Eventually, as winnings increased, all accounts were reset and prices were raised significantly. As the population in a single arena approached 30, the strain on the AreaBot became too great and it would cease to function. The ?help command was flooded with "FIX THE BOT NOW N00B STAFFS!!!" while available mods scrambled to kill the existing bot and spawn another from the hub. Over time, it got so bad that the hub itself died and had to be manually restarted by 1stStrike. This is considered the "Dark Age" of Hyperspace for the moderating team. In response to the situation, Dr Brain began working on a new system for the then unheard of and highly experimental [[ASSS]] server. The zone took a leave of absence for a few months before re-emerging as SSCX-A.

-add more-

=== Getting SSC ===

=== SSCX-A ===

[[Category: Zones]]

Hyperspace

2005-01-14T02:33:58Z

Dr Brain: Moved smods to a seperate table

SSCX-A Hyperspace was one of the first zones to adopt [[ASSS]].

== Gameplay ==

== Staff ==

<table border=0 frame=void rules=cols width=50%>
<tr>
<td align=center colspan=3><h3>Sysops</h3></td>
</tr>
<tr>
<td align=center>[[User:Dr Brain|Dr Brain]]</td>
<td align=center>Picano</td>
</tr>
</table>

<table border=0 frame=void rules=cols width=50%>
<tr>
<td align=center colspan=3><h3>Smods</h3></td>
</tr>
<tr>
<td align=center>Nerusai</td>
</tr>
</table>

<table border=0 frame=void rules=cols width=50%>
<tr>
<td align=center colspan=4><h3>Moderators</h3></td>
</tr>
<tr>
<td align=center>D1st0rt</td>
<td align=center>Coenny</td>
<td align=center>Quigybobo</td>
<td align=center>Bomook</td>
</tr>
<tr>
<td align=center>Wargh</td>
<td align=center>FunkmastaD</td>
<td align=center>[[User:Nikegurl|nikegurl]]</td>
<td align=center>Lanvalk</td>
</tr>
</table>

== History ==

=== Event Horizon ===

Hyperspace started life as a LAN zone played by a small group of friends, Dr Brain among them. They eventually decided to put it online to try and get more players in it. Having something of a scientific bent, they decided to name it ''Event Horizon'' after the point of no return surrounding black holes. The zone, once online never took off. It was briefly hosted on Can-Link before the hosting service imploded. After considering that the zone had only reached a maximum population of 4 players, the zone was abandoned and the group persued more rewarding games such as Infantry and Starcraft.

=== Dog Fight ===

Months later, Dr Brain revived the zone under the name ''Dog Fight'' with a new map. Again, nothing happened with the zone and it was closed.

=== Jeff's Zone ===

In order to experiment with [[Subgame2]] Dr Brain again hosted Dog Fight under the new name ''Jeff's Stupid Zone''. After some days of fiddling, Dr Brain finally figured out how to make Hypertunnels work. He remade the map and added some Hypertunnels around the very edge of the map. The zone's population doubled to a whole 6 players at peak times. Encouraged by this incredible population boost, more hypertunnels were added and the zone was renamed to ''Jeff's Zone''.

=== Hosting, at last ===

Ever since the collapse of Can-Link, the zone had been hosted by Dr Brain on his cable connection. This lead to occasional downtime because of computer crashes and also to more lag than was preferable. SSDZ offered its services and the zone was moved.

=== Hyperspace ===

Dr Brain felt, now that the zone was picking up, that the name ''Jeff's Zone'' was no longer good enough. So, he started asking the player population about new name ideas. Someone suggested the name ''Hyperspeed'' and everyone agreed that it was a great name. Somehow, Dr Brain forgot the exact details of the name and changed the name to ''Hyperspace''. Only later did he realize that everyone had agreed to ''Hyperspeed'', but by then, it was too late to change.

=== Project 0 ===

This zone was created mainly for graphics testing but later on became "known" for a small heavily bot maintained arena called Warp2 (warpto joke). Many colorful graphics and anime girls (specifically catgirls) were featured here.

Average population was around eight and at max 14, not counting 6 bots (only 1 full time).

=== SSXH ===

The intermittent failures of SSDZ lead Dr Brain and picano2.0 to search for new hosting. SSXH under Delta_5 agreed to host the zone and a long period of properity for Hyperspace started.

=== SSND/SSDX ===

Eventually, SSXH decided to close down. A new host was needed and the SSDX network accepted Hyperspace. After a merger between SSDX and SSN, and several moves between servers on the SSN network, Hyperspace eventually settled down. Unfortuantly, the peace was not to last. Within weeks of quieting down, SSN closed down for no obvious reason.

=== SSI ===

Due to the collapse of SSN, Hyperspace was again hostless and had to be hosted by Dr Brain's less-than-perfect connection. Eventually, hosting was secured from SSI (run by 1stStrike and Argyle). Again, the zone flourished.

=== TWCore & AreaBot ===

As part of the SSI hosting package, Hyperspace developers were given access to the [[TWCore]] bot system (at the time, it was not public access). Everything was great for a while with small populations, but changes were needed to support the growing population. Initially, all kills gave 50 'HS Bucks'. This was changed to an earnings formula by [[User:D1st0rt|D1st0rt]] which was roughly 1+(killed bty / killer bty) * 50. Eventually, as winnings increased, all accounts were reset and prices were raised significantly. As the population in a single arena approached 30, the strain on the AreaBot became too great and it would cease to function. The ?help command was flooded with "FIX THE BOT NOW N00B STAFFS!!!" while available mods scrambled to kill the existing bot and spawn another from the hub. Over time, it got so bad that the hub itself died and had to be manually restarted by 1stStrike. This is considered the "Dark Age" of Hyperspace for the moderating team. In response to the situation, Dr Brain began working on a new system for the then unheard of and highly experimental [[ASSS]] server. The zone took a leave of absence for a few months before re-emerging as SSCX-A.

-add more-

=== Getting SSC ===

=== SSCX-A ===

[[Category: Zones]]

Hyperspace

2005-01-14T02:30:35Z

Dr Brain: Linked nikegurl

SSCX-A Hyperspace was one of the first zones to adopt [[ASSS]].

== Gameplay ==

== Staff ==

<table border=0 frame=void rules=cols width=50%>
<tr>
<td align=center colspan=3><h3>Sysops and Smods</h3></td>
</tr>
<tr>
<td align=center>[[User:Dr Brain|Dr Brain]]</td>
<td align=center>Picano</td>
<td align=center>Nerusai</td>
</tr>
</table>

<table border=0 frame=void rules=cols width=50%>
<tr>
<td align=center colspan=4><h3>Moderators</h3></td>
</tr>
<tr>
<td align=center>D1st0rt</td>
<td align=center>Coenny</td>
<td align=center>Quigybobo</td>
<td align=center>Bomook</td>
</tr>
<tr>
<td align=center>Wargh</td>
<td align=center>FunkmastaD</td>
<td align=center>[[User:Nikegurl|nikegurl]]</td>
<td align=center>Lanvalk</td>
</tr>
</table>

== History ==

=== Event Horizon ===

Hyperspace started life as a LAN zone played by a small group of friends, Dr Brain among them. They eventually decided to put it online to try and get more players in it. Having something of a scientific bent, they decided to name it ''Event Horizon'' after the point of no return surrounding black holes. The zone, once online never took off. It was briefly hosted on Can-Link before the hosting service imploded. After considering that the zone had only reached a maximum population of 4 players, the zone was abandoned and the group persued more rewarding games such as Infantry and Starcraft.

=== Dog Fight ===

Months later, Dr Brain revived the zone under the name ''Dog Fight'' with a new map. Again, nothing happened with the zone and it was closed.

=== Jeff's Zone ===

In order to experiment with [[Subgame2]] Dr Brain again hosted Dog Fight under the new name ''Jeff's Stupid Zone''. After some days of fiddling, Dr Brain finally figured out how to make Hypertunnels work. He remade the map and added some Hypertunnels around the very edge of the map. The zone's population doubled to a whole 6 players at peak times. Encouraged by this incredible population boost, more hypertunnels were added and the zone was renamed to ''Jeff's Zone''.

=== Hosting, at last ===

Ever since the collapse of Can-Link, the zone had been hosted by Dr Brain on his cable connection. This lead to occasional downtime because of computer crashes and also to more lag than was preferable. SSDZ offered its services and the zone was moved.

=== Hyperspace ===

Dr Brain felt, now that the zone was picking up, that the name ''Jeff's Zone'' was no longer good enough. So, he started asking the player population about new name ideas. Someone suggested the name ''Hyperspeed'' and everyone agreed that it was a great name. Somehow, Dr Brain forgot the exact details of the name and changed the name to ''Hyperspace''. Only later did he realize that everyone had agreed to ''Hyperspeed'', but by then, it was too late to change.

=== Project 0 ===

This zone was created mainly for graphics testing but later on became "known" for a small heavily bot maintained arena called Warp2 (warpto joke). Many colorful graphics and anime girls (specifically catgirls) were featured here.

Average population was around eight and at max 14, not counting 6 bots (only 1 full time).

=== SSXH ===

The intermittent failures of SSDZ lead Dr Brain and picano2.0 to search for new hosting. SSXH under Delta_5 agreed to host the zone and a long period of properity for Hyperspace started.

=== SSND/SSDX ===

Eventually, SSXH decided to close down. A new host was needed and the SSDX network accepted Hyperspace. After a merger between SSDX and SSN, and several moves between servers on the SSN network, Hyperspace eventually settled down. Unfortuantly, the peace was not to last. Within weeks of quieting down, SSN closed down for no obvious reason.

=== SSI ===

Due to the collapse of SSN, Hyperspace was again hostless and had to be hosted by Dr Brain's less-than-perfect connection. Eventually, hosting was secured from SSI (run by 1stStrike and Argyle). Again, the zone flourished.

=== TWCore & AreaBot ===

As part of the SSI hosting package, Hyperspace developers were given access to the [[TWCore]] bot system (at the time, it was not public access). Everything was great for a while with small populations, but changes were needed to support the growing population. Initially, all kills gave 50 'HS Bucks'. This was changed to an earnings formula by [[User:D1st0rt|D1st0rt]] which was roughly 1+(killed bty / killer bty) * 50. Eventually, as winnings increased, all accounts were reset and prices were raised significantly. As the population in a single arena approached 30, the strain on the AreaBot became too great and it would cease to function. The ?help command was flooded with "FIX THE BOT NOW N00B STAFFS!!!" while available mods scrambled to kill the existing bot and spawn another from the hub. Over time, it got so bad that the hub itself died and had to be manually restarted by 1stStrike. This is considered the "Dark Age" of Hyperspace for the moderating team. In response to the situation, Dr Brain began working on a new system for the then unheard of and highly experimental [[ASSS]] server. The zone took a leave of absence for a few months before re-emerging as SSCX-A.

-add more-

=== Getting SSC ===

=== SSCX-A ===

[[Category: Zones]]

User:Nikegurl

2005-01-14T02:29:52Z

Dr Brain: Moved from SSCX-A Hyperspace

== History with SSCX-A Hyperspace ==

nikegurl (originally NiKe G u R L 637) has been old, old friends with picano and other members of Hyperspace for quite some time, stemming back from their Lasertag years (a TW subarena). When Lasertag was collapsing and becoming less and less popular, nikegurl wanted to search for a new, just as close-knite and welcoming zone. Power_P invited her to "Hyperspace", and when she arrived, he promptly granted her $10,000.

Originally, "Nike" was not too into Hyperspace, as she didn't really know anyone, and was much less outgoing than she is now. She also disliked the frequent bot-crashing (botRdead again). She quit Subspace for a long time during the time that Hyperspace was changing from SSI to SSCX, and then came back when Hyperspace was up again.

But something had changed this time. She was much more friendly and talkative, and made "friends" easily among the staff (=P). Soon, the staff began appreciating her beauty and devotion (or maybe something else...) and voted her in as a junior-moderator with FunkmastaD (much to the disgust of then known as Siaon). Many accused her of using her feminine charms to obtain votes, but this isn't true. At all. Yup.

She had a lot to learn. Soon enough, she became a popular and well-loved and just mod, that was a little ban-happy. But she upheld the rules, and that made staff happy. There were many incidents during her time, such as many pictures of males shown to her, several of her pictures been shown and sold (including photoshopped catgirl ones, to the delight of picano), and catgirl stuff, and many really sexual-related quotes now floating around quotes.ssforum.net

One of her main roles in HS is banning people, throwing jalapenos in player's eyes, making totally random arena messages, keeping the staff chat lively and NC-17, and being on winning flagging teams.

Hyperspace

2005-01-14T02:11:42Z

Dr Brain: /* Dr Brain */

SSCX-A Hyperspace was one of the first zones to adopt ASSS.

== Gameplay ==

== Staff ==

=== Sysops and Smods ===

==== Dr Brain ====

Dr Brain is the founder of Hyperspace and one of the two zone owners. He has been with the zone since it was just a LAN server between friends.

Dr Brain was one of the writers of the Area bots that gave Hyperspace the buy system that now defines it. He also ported the bot to a set of ASSS modules when the zone switched to SSCX-A.

He, along with Nerusai, oversee the continuing development of the Hyperspace modules.

His offical job in the zone is to maintain and develop the public arena. This includes settings, map, and graphics.

He is also the only surviving member of the squad Darksaber.

==== Picano ====

==== Nerusai ====

=== Moderators ===

==== D1st0rt ====

==== Coenny ====

==== Quigybobo ====

==== Bomook ====

==== Wargh ====

==== FunkmastaD ====

==== nikegurl ====

==== Lanvalk ====

== History ==

=== Event Horizon ===

Hyperspace started life as a LAN zone played by a small group of friends, Dr Brain among them. They eventually decided to put it online to try and get more players in it. Having something of a scientific bent, they decided to name it ''Event Horizon'' after the point of no return surrounding black holes. The zone, once online never took off. It was briefly hosted on Can-Link before the hosting service imploded. After considering that the zone had only reached a maximum population of 4 players, the zone was abandoned and the group persued more rewarding games such as Infantry and Starcraft.

=== Dog Fight ===

Months later, Dr Brain revived the zone under the name ''Dog Fight'' with a new map. Again, nothing happened with the zone and it was closed.

=== Jeff's Zone ===

In order to experiment with [[Subgame2]] Dr Brain again hosted Dog Fight under the new name ''Jeff's Stupid Zone''. After some days of fiddling, Dr Brain finally figured out how to make Hypertunnels work. He remade the map and added some Hypertunnels around the very edge of the map. The zone's population doubled to a whole 6 players at peak times. Encouraged by this incredible population boost, more hypertunnels were added and the zone was renamed to ''Jeff's Zone''.

=== Hosting, at last ===

Ever since the collapse of Can-Link, the zone had been hosted by Dr Brain on his cable connection. This lead to occasional downtime because of computer crashes and also to more lag than was preferable. SSDZ offered its services and the zone was moved.

=== Hyperspace ===

Dr Brain felt, now that the zone was picking up, that the name ''Jeff's Zone'' was no longer good enough. So, he started asking the player population about new name ideas. Someone suggested the name ''Hyperspeed'' and everyone agreed that it was a great name. Somehow, Dr Brain forgot the exact details of the name and changed the name to ''Hyperspace''. Only later did he realize that everyone had agreed to ''Hyperspeed'', but by then, it was too late to change.

=== Project 0 ===

This zone was created mainly for graphics testing but later on became "known" for a small heavily bot maintained arena called Warp2 (warpto joke). Many colorful graphics and anime girls (specifically catgirls) were featured here.

Average population was around eight and at max 14, not counting 6 bots (only 1 full time).

=== SSXH ===

The intermittent failures of SSDZ lead Dr Brain and picano2.0 to search for new hosting. SSXH under Delta_5 agreed to host the zone and a long period of properity for Hyperspace started.

=== SSND/SSDX ===

Eventually, SSXH decided to close down. A new host was needed and the SSDX network accepted Hyperspace. After a merger between SSDX and SSN, and several moves between servers on the SSN network, Hyperspace eventually settled down. Unfortuantly, the peace was not to last. Within weeks of quieting down, SSN closed down for no obvious reason.

=== SSI ===

Due to the collapse of SSN, Hyperspace was again hostless and had to be hosted by Dr Brain's less-than-perfect connection. Eventually, hosting was secured from SSI (run by 1stStrike and Argyle). Again, the zone flourished.

=== TWCore & AreaBot ===

As part of the SSI hosting package, Hyperspace developers were given access to the [[TWCore]] bot system (at the time, it was not public access).

-add more-

=== Getting SSC ===

=== SSCX-A ===

[[Category: Zones]]

Hyperspace

2005-01-14T02:05:56Z

Dr Brain: Fixed the nikegurl mess

SSCX-A Hyperspace was one of the first zones to adopt ASSS.

== Gameplay ==

== Staff ==

=== Sysops and Smods ===

==== Dr Brain ====

==== Picano ====

==== Nerusai ====

=== Moderators ===

==== D1st0rt ====

==== Coenny ====

==== Quigybobo ====

==== Bomook ====

==== Wargh ====

==== FunkmastaD ====

==== nikegurl ====

==== Lanvalk ====

== History ==

=== Event Horizon ===

Hyperspace started life as a LAN zone played by a small group of friends, Dr Brain among them. They eventually decided to put it online to try and get more players in it. Having something of a scientific bent, they decided to name it ''Event Horizon'' after the point of no return surrounding black holes. The zone, once online never took off. It was briefly hosted on Can-Link before the hosting service imploded. After considering that the zone had only reached a maximum population of 4 players, the zone was abandoned and the group persued more rewarding games such as Infantry and Starcraft.

=== Dog Fight ===

Months later, Dr Brain revived the zone under the name ''Dog Fight'' with a new map. Again, nothing happened with the zone and it was closed.

=== Jeff's Zone ===

In order to experiment with [[Subgame2]] Dr Brain again hosted Dog Fight under the new name ''Jeff's Stupid Zone''. After some days of fiddling, Dr Brain finally figured out how to make Hypertunnels work. He remade the map and added some Hypertunnels around the very edge of the map. The zone's population doubled to a whole 6 players at peak times. Encouraged by this incredible population boost, more hypertunnels were added and the zone was renamed to ''Jeff's Zone''.

=== Hosting, at last ===

Ever since the collapse of Can-Link, the zone had been hosted by Dr Brain on his cable connection. This lead to occasional downtime because of computer crashes and also to more lag than was preferable. SSDZ offered its services and the zone was moved.

=== Hyperspace ===

Dr Brain felt, now that the zone was picking up, that the name ''Jeff's Zone'' was no longer good enough. So, he started asking the player population about new name ideas. Someone suggested the name ''Hyperspeed'' and everyone agreed that it was a great name. Somehow, Dr Brain forgot the exact details of the name and changed the name to ''Hyperspace''. Only later did he realize that everyone had agreed to ''Hyperspeed'', but by then, it was too late to change.

=== Project 0 ===

This zone was created mainly for graphics testing but later on became "known" for a small heavily bot maintained arena called Warp2 (warpto joke). Many colorful graphics and anime girls (specifically catgirls) were featured here.

Average population was around eight and at max 14, not counting 6 bots (only 1 full time).

=== SSXH ===

The intermittent failures of SSDZ lead Dr Brain and picano2.0 to search for new hosting. SSXH under Delta_5 agreed to host the zone and a long period of properity for Hyperspace started.

=== SSND/SSDX ===

Eventually, SSXH decided to close down. A new host was needed and the SSDX network accepted Hyperspace. After a merger between SSDX and SSN, and several moves between servers on the SSN network, Hyperspace eventually settled down. Unfortuantly, the peace was not to last. Within weeks of quieting down, SSN closed down for no obvious reason.

=== SSI ===

Due to the collapse of SSN, Hyperspace was again hostless and had to be hosted by Dr Brain's less-than-perfect connection. Eventually, hosting was secured from SSI (run by 1stStrike and Argyle). Again, the zone flourished.

=== TWCore & AreaBot ===

As part of the SSI hosting package, Hyperspace developers were given access to the [[TWCore]] bot system (at the time, it was not public access).

-add more-

=== Getting SSC ===

=== SSCX-A ===

[[Category: Zones]]

Hyperspace

2005-01-13T19:21:53Z

Dr Brain: /* SSND/SSDX */ Minor historical note

SSCX-A Hyperspace was one of the first zones to adopt ASSS.

== Gameplay ==

== Staff ==

=== Sysops and Smods ===

==== Dr Brain ====

==== Picano ====

==== Nerusai ====

=== Moderators ===

==== D1st0rt ====

==== Coenny ====

==== Quigybobo ====

==== Bomook ====

==== Wargh ====

==== FunkmastaD ====

==== nikegurl ====

==== Lanvalk ====

== History ==

=== Event Horizon ===

Hyperspace started life as a LAN zone played by a small group of friends, Dr Brain among them. They eventually decided to put it online to try and get more players in it. Having something of a scientific bent, they decided to name it ''Event Horizon'' after the point of no return surrounding black holes. The zone, once online never took off. It was briefly hosted on Can-Link before the hosting service imploded. After considering that the zone had only reached a maximum population of 4 players, the zone was abandoned and the group persued more rewarding games such as Infantry and Starcraft.

=== Dog Fight ===

Months later, Dr Brain revived the zone under the name ''Dog Fight'' with a new map. Again, nothing happened with the zone and it was closed.

=== Jeff's Zone ===

In order to experiment with [[Subgame2]] Dr Brain again hosted Dog Fight under the new name ''Jeff's Stupid Zone''. After some days of fiddling, Dr Brain finally figured out how to make Hypertunnels work. He remade the map and added some Hypertunnels around the very edge of the map. The zone's population doubled to a whole 6 players at peak times. Encouraged by this incredible population boost, more hypertunnels were added and the zone was renamed to ''Jeff's Zone''.

=== Hosting, at last ===

Ever since the collapse of Can-Link, the zone had been hosted by Dr Brain on his cable connection. This lead to occasional downtime because of computer crashes and also to more lag than was preferable. SSDZ offered its services and the zone was moved.

=== Hyperspace ===

Dr Brain felt, now that the zone was picking up, that the name ''Jeff's Zone'' was no longer good enough. So, he started asking the player population about new name ideas. Someone suggested the name ''Hyperspeed'' and everyone agreed that it was a great name. Somehow, Dr Brain forgot the exact details of the name and changed the name to ''Hyperspace''. Only later did he realize that everyone had agreed to ''Hyperspeed'', but by then, it was too late to change.

=== Project 0 ===

-add more-

=== SSXH ===

The intermittent failures of SSDZ lead Dr Brain and picano2.0 to search for new hosting. SSXH under Delta_5 agreed to host the zone and a long period of properity for Hyperspace started.

=== SSND/SSDX ===

Eventually, SSXH decided to close down. A new host was needed and the SSDX network accepted Hyperspace. After a merger between SSDX and SSN, and several moves between servers on the SSN network, Hyperspace eventually settled down. Unfortuantly, the peace was not to last. Within weeks of quieting down, SSN closed down for no obvious reason.

=== SSI ===

Due to the collapse of SSN, Hyperspace was again hostless and had to be hosted by Dr Brain's less-than-perfect connection. Eventually, hosting was secured from SSI (run by 1stStrike and Argyle). Again, the zone flourished.

=== TWCore & AreaBot ===

As part of the SSI hosting package, Hyperspace developers were given access to the [[TWCore]] bot system (at the time, it was not public access).

-add more-

=== Getting SSC ===

=== SSCX-A ===

[[Category: Zones]]

Hyperspace

2005-01-13T19:19:31Z

Dr Brain: Added more content

SSCX-A Hyperspace was one of the first zones to adopt ASSS.

== Gameplay ==

== Staff ==

=== Sysops and Smods ===

==== Dr Brain ====

==== Picano ====

==== Nerusai ====

=== Moderators ===

==== D1st0rt ====

==== Coenny ====

==== Quigybobo ====

==== Bomook ====

==== Wargh ====

==== FunkmastaD ====

==== nikegurl ====

==== Lanvalk ====

== History ==

=== Event Horizon ===

Hyperspace started life as a LAN zone played by a small group of friends, Dr Brain among them. They eventually decided to put it online to try and get more players in it. Having something of a scientific bent, they decided to name it ''Event Horizon'' after the point of no return surrounding black holes. The zone, once online never took off. It was briefly hosted on Can-Link before the hosting service imploded. After considering that the zone had only reached a maximum population of 4 players, the zone was abandoned and the group persued more rewarding games such as Infantry and Starcraft.

=== Dog Fight ===

Months later, Dr Brain revived the zone under the name ''Dog Fight'' with a new map. Again, nothing happened with the zone and it was closed.

=== Jeff's Zone ===

In order to experiment with [[Subgame2]] Dr Brain again hosted Dog Fight under the new name ''Jeff's Stupid Zone''. After some days of fiddling, Dr Brain finally figured out how to make Hypertunnels work. He remade the map and added some Hypertunnels around the very edge of the map. The zone's population doubled to a whole 6 players at peak times. Encouraged by this incredible population boost, more hypertunnels were added and the zone was renamed to ''Jeff's Zone''.

=== Hosting, at last ===

Ever since the collapse of Can-Link, the zone had been hosted by Dr Brain on his cable connection. This lead to occasional downtime because of computer crashes and also to more lag than was preferable. SSDZ offered its services and the zone was moved.

=== Hyperspace ===

Dr Brain felt, now that the zone was picking up, that the name ''Jeff's Zone'' was no longer good enough. So, he started asking the player population about new name ideas. Someone suggested the name ''Hyperspeed'' and everyone agreed that it was a great name. Somehow, Dr Brain forgot the exact details of the name and changed the name to ''Hyperspace''. Only later did he realize that everyone had agreed to ''Hyperspeed'', but by then, it was too late to change.

=== Project 0 ===

-add more-

=== SSXH ===

The intermittent failures of SSDZ lead Dr Brain and picano2.0 to search for new hosting. SSXH under Delta_5 agreed to host the zone and a long period of properity for Hyperspace started.

=== SSND/SSDX ===

Eventually, SSXH decided to close down. A new host was needed and the SSDX network accepted Hyperspace. After several moves between servers on the SSN network, Hyperspace eventually settled down.

=== SSI ===

Due to the collapse of SSN, Hyperspace was again hostless and had to be hosted by Dr Brain's less-than-perfect connection. Eventually, hosting was secured from SSI (run by 1stStrike and Argyle). Again, the zone flourished.

=== TWCore & AreaBot ===

As part of the SSI hosting package, Hyperspace developers were given access to the [[TWCore]] bot system (at the time, it was not public access).

-add more-

=== Getting SSC ===

=== SSCX-A ===

[[Category: Zones]]

Hyperspace

2005-01-13T18:33:49Z

Dr Brain: Added some early history

Hyperspace

2005-01-13T15:38:48Z

Dr Brain: Added outline

Zones

2005-01-13T15:14:58Z

Dr Brain: Added a link to Hyperspace

A zone is an independently developed game that is playable through [[Continuum]]. Zones are hosted on [[servers]], and each zone is unique to the next. [[SSC]] Zones are all on the Subspace Central network. This is the most secure network to play on, and is the oldest. Most zones strive to attain quality in order to become an [[SSC]] zone.

==SSC Zones==
===SFSS Zones===
*SFSS Ground Warfare (SSC)
*SFSS Star Wars (SSC)
*SFSS SuB-iCiDe (SSC)
===SSCC Zones===
*SSCC Halo CTF
*SSCC Metal Gear CTF
===SSCE Zones===
*SSCE Hockey Zone
===SSCI Zones===
*SSCI Dragonball Z
*SSCI Gundam Wing
*SSCI Super Ships
===SSCU Zones===
*[[17th Parallel|SSCU 17th Parallel]]
*SSCU Death Star Battle
*[[Redstar|SSCU Redstar]]
*SSCU Trench Wars

===SSCX Zones===
*SSCX Alpha West SVS
*SSCX Chaos/League Zone SVS
*SSCX Dueling Arizona SVS
*SSCX Extreme-Games
*SSCX Powerball
*SSCX Star Wars Realm
*SSCX Star Warzone
*SSCX Warzone/ASWZ CTF
*SSCX-A BattleZone
*SSCX-A GTA
*[[Hyperspace|SSCX-A Hyperspace]]
===T3===
*T3 The Gauntlet! (SSC)

==Non SSC Zones==
===SSI Zones===
*SSI Flagging Turmoil
===SSN Zones===
*SSN Assault
*SSN South Tejas
*SSN Trust & Betrayal
*SSN Ultima Fire
*SSN Sniper
===SSZ Zones===
*SSZ Battle Field 1942
*SSZ Counter Strike
*SSZ Desert Storm
*SSZ FLAG HELL
*SSZ Lethal Weapon
*SSZ Mystic Kingdom
*[http://www.omega-fire.com SSZ Omega Fire]
*SSZ RPG World
*SSZ Zelda MotW

==League Zones==
===SSCU Zones===
*DSB LEAGUE
===SSCX Zones===
*Star Warzone League

==Development/Test Zones==
===SSI Zones===
*TWDev Testing
===SSZ Zones===
*Beef's Dev zone 1.0
*SSZ United Development
===Unknown Server===
*A81> Test Zone
*asss test server
*asss test (powerball arena)
*Hyperspace Test

[[Category: Definitions]]

User:Dr Brain

2005-01-11T23:20:54Z

Dr Brain: Rewrote for the third person.

Dr Brain is the owner and operator of SSCX-A Hyperspace. He was one of the first zone owners to switch over to ASSS. He is rarely seen outside of Hyperspace, though on the few occasions that it happens it is usually to help someone debug their ASSS setup.

Dr Brain oversees all ASSS related activity that happens in Hyperspace and is the person you should contact if you are interested in writing modules for HS.

Writing Modules for Hyperspace

2005-01-11T19:19:26Z

Dr Brain: Added detail the the item stuff

== Getting Started ==

The first thing you should do is check with Dr Brain to make sure someone else isn't already making a similar module. The best way to contact him is either in game (PM/?message) or via AIM/ICQ (check the Hyperspace news file).

== General Info ==

In general, hard coding values is frowned upon. Please try to use the arena and global configs wherever possible. Put a sensible default into the '''GetInt''' so that not every config entry needs to be present for the module to work.

== Naming ==

Because of module naming conflicts, all official Hyperspace related modules are prefixed with hs_. So, for example, a kill spree module becomes hs_spree. This is not required for module submissions. You are free to name your module whatever you wish.

== Style ==

There is a Hyperspace standard style for formatting code, but it is completely optional. You should make your interface headers easy to read, though.

Here is an example of the Hyperspace official style:

''hs_twowords.h'':
<pre>
#ifndef HS_TWOWORDS_H
#define HS_TWOWORDS_H

#define I_HS_TWOWORDS "hs_twowords-1"

typedef struct Ihstwowords
{
INTERFACE_HEAD_DECL

int (*interfaceFunction)(Player *p);
} Ihstwowords;

#endif //HS_TWOWORDS_H
</pre>

''hs_twowords.c'':
<pre>
#include <string.h> //optional. others added as needed

#include "asss.h"
#include "hscore.h"
#include "hs_twowords.h"

//modules
local Imodman *mm;
local Ilogman *lm;
local Ichat *chat;
local Iconfig *cfg;
local Icmdman *cmd;
local Iplayerdata *pd;

//interface prototypes
local int interfaceFunction(Player *p);

local helptext_t twoWordsHelp =
"Targets: player\n"
"Args: none\n"
"Who knows? This is just a template file.\n";

local void twoWordsCommand(const char *command, const char *params, Player *p, const Target *target)
{
if (target->type == T_PLAYER) //private command
{
Player *t = target->u.p;

//do something
}
else //not private
{
chat->SendMessage(p, "You must target a player.");
}
}

local int interfaceFunction(Player *p)
{
if (something) //space between if and ()
{
//do something
}
}

local Ihstwowords interface =
{
INTERFACE_HEAD_INIT(I_HS_TWOWORDS, "hs_twowords")
interfaceFunction
};

EXPORT int MM_hs_twowords(int action, Imodman *_mm, Arena *arena)
{
if (action == MM_LOAD)
{
mm = _mm;

lm = mm->GetInterface(I_LOGMAN, ALLARENAS);
chat = mm->GetInterface(I_CHAT, ALLARENAS);
cfg = mm->GetInterface(I_CONFIG, ALLARENAS);
cmd = mm->GetInterface(I_CMDMAN, ALLARENAS);
pd = mm->GetInterface(I_PLAYERDATA, ALLARENAS);

if (!lm || !chat || !cfg || !cmd || !pd)
{
mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(cfg);
mm->ReleaseInterface(cmd);
mm->ReleaseInterface(pd);

return MM_FAIL;
}

mm->RegInterface(&interface, ALLARENAS);

cmd->AddCommand("twowords", twoWordsCommand, ALLARENAS, twoWordsHelp);

return MM_OK;
}
else if (action == MM_UNLOAD)
{
if (mm->UnregInterface(&interface, ALLARENAS))
{
return MM_FAIL;
}

cmd->RemoveCommand("twowords", twoWordsCommand, ALLARENAS);

mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(cfg);
mm->ReleaseInterface(cmd);
mm->ReleaseInterface(pd);

return MM_OK;
}
return MM_FAIL;
}
</pre>

== Required Files ==

Here is ''hscore.h'':
<pre>
#include "hscore_types.h"

#include "hscore_money.h"
#include "hscore_items.h"
</pre>

Here is ''hscore_types.h'':
<pre>
#ifndef HSCORE_TYPES_H
#define HSCORE_TYPES_H

typedef enum EventAction
{
//removes event->data amount of the items from the ship's inventory
ACTION_REMOVE_ITEM = 0,

//removes event->data amount of the item's ammo type from inventory
ACTION_REMOVE_ITEM_AMMO,

//sends prize #event->data to the player
ACTION_PRIZE,

//sets the item's inventory data to event->data. This is useful with
//the "purchace" event.
ACTION_SET_INVENTORY_DATA,

//does a ++ on inventory data.
ACTION_INCREMENT_INVENTORY_DATA,

//does a -- on inventory data. A "datazero" event may be generated as a result.
ACTION_DECREMENT_INVENTORY_DATA,

//Specs the player.
ACTION_SPEC,

//sends a shipreset packet and reprizes all items (antideath, really)
ACTION_SHIP_RESET

//we need a lot more
} EventAction;

typedef struct Event
{
char event[16]; //something like "death" or "datazero"
EventAction action;

int data; //action dependent

char message[200]; //if == to "" then nothing will be sent.
} Event;

typedef struct Property
{
char name[16];
int value;
} Property;

typedef struct ItemType
{
char name[32];
int max; //maximum total of this item type on a ship before ?buy denies purchace

int id; //MySQL use only
} ItemType;

typedef struct Item
{
char name[16];
char shortDesc[32]; //displayed inline in the ?buy menu
char longDesc[200]; //displayed as part of ?iteminfo
int buyPrice;
int sellPrice;

int expRequired; //requirement to own

int shipsAllowed; //bit positions represent each ship. bit 0 = warbird.

LinkedList propertyList;

LinkedList eventList;

ItemType *type1, *type2;
int typeDelta1, typeDelta2;

int max;

//if changes to this item should be delayed until a complete save (like on exit).
//This is a necessity when dealing with ammo. We don't want to update MySQL every
//time a gun is fired.
int delayStatusWrite;

struct Item *ammo; //can be NULL, only for use by events.
int ammoID; //used for post processing ONLY

int id; //MySQL use only
} Item;

typedef struct InventoryEntry
{
Item *item;
int count;

int data; //persistent int for use by the event system.
} InventoryEntry;

typedef struct ShipHull
{
LinkedList inventoryEntryList;

//NOTE: no need for ship #, as it's defined by the array index (when loaded by hscore_database)

//if we compile a hashmap of properties, it can go in here.

int id; //MySQL use only
} ShipHull;

typedef struct Category
{
char name[32]; //displayed on ?buy
char description[64]; //displayed inline on the ?buy menu

LinkedList itemList; //a list of member items that are displayed

int id; //mysql use
} Category;

typedef struct Store
{
char name[32]; //displayed in ?buysell location errors
char description[200]; //displayed in ?storeinfo
char region[16]; //region that defines the store

LinkedList itemList; //a list of items that can be purchaced here

int id; //mysql use
} Store;

#endif //HSCORE_TYPES_H
</pre>

== Money and Experience ==

Money and experience points (aka exp) are what make the Hyperspace world go 'round. Nearly every Hyperspace module has some dealings with money/exp transactions of some kind.

Here is the '''hscore_money.h''' contents:

<pre>
#ifndef HSCORE_MONEY_H
#define HSCORE_MONEY_H

#define I_HSCORE_MONEY "hscore_money-1"

typedef enum MoneyType
{
//for /?give
MONEY_TYPE_GIVE = 0,

//for /?grant
MONEY_TYPE_GRANT,

//for ?buy and ?sell
MONEY_TYPE_BUYSELL,

//for money from kills
MONEY_TYPE_KILL,

//for money from flag games
MONEY_TYPE_FLAG,

//for money from soccer games
MONEY_TYPE_BALL,

//for money from module driven events
MONEY_TYPE_EVENT
} MoneyType;

#define MONEY_TYPE_COUNT 7

typedef struct Ihscoremoney
{
INTERFACE_HEAD_DECL

void (*giveMoney)(Player *p, int amount, MoneyType type);
void (*setMoney)(Player *p, int amount, MoneyType type); //beware. know what you're doing

int (*getMoney)(Player *p);
int (*getMoneyType)(Player *p, MoneyType type); //used only for /?money -d

void (*giveExp)(Player *p, int amount);
void (*setExp)(Player *p, int amount); //beware. know what you're doing

int (*getExp)(Player *p);
} Ihscoremoney;

#endif //HSCORE_MONEY_H
</pre>

=== Giving exp ===

<pre>
money->giveExp(p, 10); //gives player p 10 exp
</pre>

=== Giving money ===

The first thing to decide is which money type to give. This is mainly used for tracking purposes. If in doubt, choose '''MONEY_TYPE_EVENT'''.

*'''MONEY_TYPE_GIVE''' is for money moving from one player to another.
*'''MONEY_TYPE_GRANT''' is for money coming from a grant command
*'''MONEY_TYPE_BUYSELL''' is for ?buying and ?selling.
*'''MONEY_TYPE_KILL''' is for money gained from kills.
*'''MONEY_TYPE_FLAG''' is for money earned from winning flag games or other flag rewards.
*'''MONEY_TYPE_BALL''' is for money received from goals.
*'''MONEY_TYPE_EVENT''' is for subarena events.

Then you can simply call:
<pre>
money->giveMoney(p, 1000, MONEY_TYPE_EVENT); //gives player p $1000
</pre>

== Using Items ==

Items are the most important part of Hyperspace after money and exp. There are two parts of items that addon modules will use. These are checking for properties and calling events. While module writers cannot directly create items, they can request item modification/addition from subarena owners.

Here is a copy of ''hscore_item.h'':
<pre>
#ifndef HSCORE_ITEMS_H
#define HSCORE_ITEMS_H

#define I_HSCORE_ITEMS "hscore_items-3"

typedef struct Ihscoreitems
{
INTERFACE_HEAD_DECL

int (*getItemCount)(Player *p, Item *item, int ship);
void (*addItem)(Player *p, Item *item, int ship, int amount);

Item * (*getItemByName)(const char *name, Arena *arena);

int (*getPropertySum)(Player *p, int ship, const char *prop); //properties ARE case sensitive

void (*triggerEvent)(Player *p, int ship, const char *event);
void (*triggerEventOnItem)(Player *p, Item *item, int ship, const char *event);

int (*getFreeItemTypeSpots)(Player *p, ItemType *type, int ship);

//more required, i'm sure
} Ihscoreitems;

#endif //HSCORE_ITEMS_H
</pre>

=== Item properties ===

Most items define properties that are used to change the player's ship. Properties are totalled for each ship and are checked per ship rather than per item. Most properties are related to the spawning module. However, any item can define custom properties. For example, if you have a subway system, a module could check if a player has at least one subway token property. You can check if the property sum on the player's current ship for "subway" is greater than 0, and if it is, let them ride.

<pre>
item->getPropertySum(p, p->p_ship, "someproperty"); //Beware of spectators.
</pre>

=== Item events ===

Items define actions that happen on certain events. Any module can trigger an event. Some modules, for example, have actions on the ''death'' event. Triggering an event is as simple as making a function call to the '''hscore_item''' module. If no items have actions on the called event, nothing will happen (so make sure you don't typo the event name). Following on the previous example, when a player rides the subway, then you can call the "ridesubway" event. The Subway Token items can define an action of self removal on that event.

<pre>
item->triggerEvent(p, p->p_ship, "someevent"); //Beware of spectators.
</pre>

== Submission ==

Once your module is working properly and seems to have no bugs, then you can submit the source to Dr Brain or MichaelG for a source check. Once that's completed, the module will be compiled for the Hyperspace server and installed.

[[Category: Module]]
[[Category: Tutorial]]

Writing Modules for Hyperspace

2005-01-11T18:42:27Z

Dr Brain: added missing hscore headers

== Getting Started ==

The first thing you should do is check with Dr Brain to make sure someone else isn't already making a similar module. The best way to contact him is either in game (PM/?message) or via AIM/ICQ (check the Hyperspace news file).

== General Info ==

In general, hard coding values is frowned upon. Please try to use the arena and global configs wherever possible. Put a sensible default into the '''GetInt''' so that not every config entry needs to be present for the module to work.

== Naming ==

Because of module naming conflicts, all official Hyperspace related modules are prefixed with hs_. So, for example, a kill spree module becomes hs_spree. This is not required for module submissions. You are free to name your module whatever you wish.

== Style ==

There is a Hyperspace standard style for formatting code, but it is completely optional. You should make your interface headers easy to read, though.

Here is an example of the Hyperspace official style:

''hs_twowords.h'':
<pre>
#ifndef HS_TWOWORDS_H
#define HS_TWOWORDS_H

#define I_HS_TWOWORDS "hs_twowords-1"

typedef struct Ihstwowords
{
INTERFACE_HEAD_DECL

int (*interfaceFunction)(Player *p);
} Ihstwowords;

#endif //HS_TWOWORDS_H
</pre>

''hs_twowords.c'':
<pre>
#include <string.h> //optional. others added as needed

#include "asss.h"
#include "hscore.h"
#include "hs_twowords.h"

//modules
local Imodman *mm;
local Ilogman *lm;
local Ichat *chat;
local Iconfig *cfg;
local Icmdman *cmd;
local Iplayerdata *pd;

//interface prototypes
local int interfaceFunction(Player *p);

local helptext_t twoWordsHelp =
"Targets: player\n"
"Args: none\n"
"Who knows? This is just a template file.\n";

local void twoWordsCommand(const char *command, const char *params, Player *p, const Target *target)
{
if (target->type == T_PLAYER) //private command
{
Player *t = target->u.p;

//do something
}
else //not private
{
chat->SendMessage(p, "You must target a player.");
}
}

local int interfaceFunction(Player *p)
{
if (something) //space between if and ()
{
//do something
}
}

local Ihstwowords interface =
{
INTERFACE_HEAD_INIT(I_HS_TWOWORDS, "hs_twowords")
interfaceFunction
};

EXPORT int MM_hs_twowords(int action, Imodman *_mm, Arena *arena)
{
if (action == MM_LOAD)
{
mm = _mm;

lm = mm->GetInterface(I_LOGMAN, ALLARENAS);
chat = mm->GetInterface(I_CHAT, ALLARENAS);
cfg = mm->GetInterface(I_CONFIG, ALLARENAS);
cmd = mm->GetInterface(I_CMDMAN, ALLARENAS);
pd = mm->GetInterface(I_PLAYERDATA, ALLARENAS);

if (!lm || !chat || !cfg || !cmd || !pd)
{
mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(cfg);
mm->ReleaseInterface(cmd);
mm->ReleaseInterface(pd);

return MM_FAIL;
}

mm->RegInterface(&interface, ALLARENAS);

cmd->AddCommand("twowords", twoWordsCommand, ALLARENAS, twoWordsHelp);

return MM_OK;
}
else if (action == MM_UNLOAD)
{
if (mm->UnregInterface(&interface, ALLARENAS))
{
return MM_FAIL;
}

cmd->RemoveCommand("twowords", twoWordsCommand, ALLARENAS);

mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(cfg);
mm->ReleaseInterface(cmd);
mm->ReleaseInterface(pd);

return MM_OK;
}
return MM_FAIL;
}
</pre>

== Required Files ==

Here is ''hscore.h'':
<pre>
#include "hscore_types.h"

#include "hscore_money.h"
#include "hscore_items.h"
</pre>

Here is ''hscore_types.h'':
<pre>
#ifndef HSCORE_TYPES_H
#define HSCORE_TYPES_H

typedef enum EventAction
{
//removes event->data amount of the items from the ship's inventory
ACTION_REMOVE_ITEM = 0,

//removes event->data amount of the item's ammo type from inventory
ACTION_REMOVE_ITEM_AMMO,

//sends prize #event->data to the player
ACTION_PRIZE,

//sets the item's inventory data to event->data. This is useful with
//the "purchace" event.
ACTION_SET_INVENTORY_DATA,

//does a ++ on inventory data.
ACTION_INCREMENT_INVENTORY_DATA,

//does a -- on inventory data. A "datazero" event may be generated as a result.
ACTION_DECREMENT_INVENTORY_DATA,

//Specs the player.
ACTION_SPEC,

//sends a shipreset packet and reprizes all items (antideath, really)
ACTION_SHIP_RESET

//we need a lot more
} EventAction;

typedef struct Event
{
char event[16]; //something like "death" or "datazero"
EventAction action;

int data; //action dependent

char message[200]; //if == to "" then nothing will be sent.
} Event;

typedef struct Property
{
char name[16];
int value;
} Property;

typedef struct ItemType
{
char name[32];
int max; //maximum total of this item type on a ship before ?buy denies purchace

int id; //MySQL use only
} ItemType;

typedef struct Item
{
char name[16];
char shortDesc[32]; //displayed inline in the ?buy menu
char longDesc[200]; //displayed as part of ?iteminfo
int buyPrice;
int sellPrice;

int expRequired; //requirement to own

int shipsAllowed; //bit positions represent each ship. bit 0 = warbird.

LinkedList propertyList;

LinkedList eventList;

ItemType *type1, *type2;
int typeDelta1, typeDelta2;

int max;

//if changes to this item should be delayed until a complete save (like on exit).
//This is a necessity when dealing with ammo. We don't want to update MySQL every
//time a gun is fired.
int delayStatusWrite;

struct Item *ammo; //can be NULL, only for use by events.
int ammoID; //used for post processing ONLY

int id; //MySQL use only
} Item;

typedef struct InventoryEntry
{
Item *item;
int count;

int data; //persistent int for use by the event system.
} InventoryEntry;

typedef struct ShipHull
{
LinkedList inventoryEntryList;

//NOTE: no need for ship #, as it's defined by the array index (when loaded by hscore_database)

//if we compile a hashmap of properties, it can go in here.

int id; //MySQL use only
} ShipHull;

typedef struct Category
{
char name[32]; //displayed on ?buy
char description[64]; //displayed inline on the ?buy menu

LinkedList itemList; //a list of member items that are displayed

int id; //mysql use
} Category;

typedef struct Store
{
char name[32]; //displayed in ?buysell location errors
char description[200]; //displayed in ?storeinfo
char region[16]; //region that defines the store

LinkedList itemList; //a list of items that can be purchaced here

int id; //mysql use
} Store;

#endif //HSCORE_TYPES_H
</pre>

== Money and Experience ==

Money and experience points (aka exp) are what make the Hyperspace world go 'round. Nearly every Hyperspace module has some dealings with money/exp transactions of some kind.

Here is the '''hscore_money.h''' contents:

<pre>
#ifndef HSCORE_MONEY_H
#define HSCORE_MONEY_H

#define I_HSCORE_MONEY "hscore_money-1"

typedef enum MoneyType
{
//for /?give
MONEY_TYPE_GIVE = 0,

//for /?grant
MONEY_TYPE_GRANT,

//for ?buy and ?sell
MONEY_TYPE_BUYSELL,

//for money from kills
MONEY_TYPE_KILL,

//for money from flag games
MONEY_TYPE_FLAG,

//for money from soccer games
MONEY_TYPE_BALL,

//for money from module driven events
MONEY_TYPE_EVENT
} MoneyType;

#define MONEY_TYPE_COUNT 7

typedef struct Ihscoremoney
{
INTERFACE_HEAD_DECL

void (*giveMoney)(Player *p, int amount, MoneyType type);
void (*setMoney)(Player *p, int amount, MoneyType type); //beware. know what you're doing

int (*getMoney)(Player *p);
int (*getMoneyType)(Player *p, MoneyType type); //used only for /?money -d

void (*giveExp)(Player *p, int amount);
void (*setExp)(Player *p, int amount); //beware. know what you're doing

int (*getExp)(Player *p);
} Ihscoremoney;

#endif //HSCORE_MONEY_H
</pre>

=== Giving exp ===

<pre>
money->giveExp(p, 10); //gives player p 10 exp
</pre>

=== Giving money ===
The first thing to decide is which money type to give. This is mainly used for tracking purposes. If in doubt, choose '''MONEY_TYPE_EVENT'''.

*'''MONEY_TYPE_GIVE''' is for money moving from one player to another.
*'''MONEY_TYPE_GRANT''' is for money coming from a grant command
*'''MONEY_TYPE_BUYSELL''' is for ?buying and ?selling.
*'''MONEY_TYPE_KILL''' is for money gained from kills.
*'''MONEY_TYPE_FLAG''' is for money earned from winning flag games or other flag rewards.
*'''MONEY_TYPE_BALL''' is for money received from goals.
*'''MONEY_TYPE_EVENT''' is for subarena events.

Then you can simply call:
<pre>
money->giveMoney(p, 1000, MONEY_TYPE_EVENT); //gives player p $1000
</pre>

== Using Items ==

Items are the most important part of Hyperspace after money and exp. There are two parts of items that addon modules will use. These are checking for properties and calling events.

Here is a copy of ''hscore_item.h'':
<pre>
#ifndef HSCORE_ITEMS_H
#define HSCORE_ITEMS_H

#define I_HSCORE_ITEMS "hscore_items-3"

typedef struct Ihscoreitems
{
INTERFACE_HEAD_DECL

int (*getItemCount)(Player *p, Item *item, int ship);
void (*addItem)(Player *p, Item *item, int ship, int amount);

Item * (*getItemByName)(const char *name, Arena *arena);

int (*getPropertySum)(Player *p, int ship, const char *prop); //properties ARE case sensitive

void (*triggerEvent)(Player *p, int ship, const char *event);
void (*triggerEventOnItem)(Player *p, Item *item, int ship, const char *event);

int (*getFreeItemTypeSpots)(Player *p, ItemType *type, int ship);

//more required, i'm sure
} Ihscoreitems;

#endif //HSCORE_ITEMS_H
</pre>

=== Item properties ===

Most items define properties that are used to change the player's ship. Properties are totalled for each ship and are checked per ship rather than per item. Most properties are related to the spawning module. However, any item can define custom properties.

<pre>
item->getPropertySum(p, p->p_ship, "someproperty"); //Beware of spectators.
</pre>

=== Item events ===

Items define actions that happen on certain events. Any module can trigger an event. Some modules, for example, have actions on the ''death'' event. Triggering an event is as simple as making a function call to the '''hscore_item''' module. If no items have actions on the called event, nothing will happen (so make sure you don't typo the event name).

<pre>
item->triggerEvent(p, p->p_ship, "someevent"); //Beware of spectators.
</pre>

== Submission ==

Once your module is working properly and seems to have no bugs, then you can submit the source to Dr Brain or MichaelG for a source check. Once that's completed, the module will be compiled for the Hyperspace server and installed.

[[Category: Module]]
[[Category: Tutorial]]

Server General Faq

2005-01-11T17:08:47Z

Dr Brain: /* Why not just use a bot? */ Removed false statements and added some better ones

== What is ASSS? ==
A Small Subspace Server (ASSS) is a replacement for subgame. It is not a clone therefore somethings will be different such as commands or the format of output from commands (grr).

I expect it uses less system resources to run as well (unlike cpu hogging subgame). '''Someone confirm this please'''

== Why is ASSS better than subgame? ==

== Does it run on Windows? ==

Yes. Grelminar maintains a windows build in addition to his linux build.

== Does it run on Linux? ==

Yes. ASSS was designed primarily for Linux and therefore works wonderfully on it.

== How hard is it to install? ==
Dead simple if you know what you are doing. But it can be like moving a mountain if you don't know how to double click.

== Why not just use a bot? ==

ASSS can simply do more than bots can.

*Because modules are a direct part of the server, things like stats and points can be easily manipulated using ASSS.
*New game types can be added so that they mesh seamlessly with everything else.
*Spawning new bots for every new subarena is not only a pain, it is sometime impractical. ASSS modules are there as soon as the new subarena is created.
*You can use server side commands. You won't ever have to cycle through your recent private message list to PM a bot again.

[[Category: Server]]
[[Category: FAQ]]

Writing Modules for Hyperspace

2005-01-11T16:59:57Z

Dr Brain: Removed edit lock text

Writing Modules for Hyperspace

2005-01-11T16:59:13Z

Dr Brain: Added all the content

I am editing. This may take a while. -- Dr Brain

== Getting Started ==

The first thing you should do is check with Dr Brain to make sure someone else isn't already making a similar module. The best way to contact him is either in game (PM/?message) or via AIM/ICQ (check the Hyperspace news file).

== General Info ==

In general, hard coding values is frowned upon. Please try to use the arena and global configs wherever possible. Put a sensable default into the '''GetInt''' so that not every config entry needs to be present for the module to work.

== Naming ==

Because of module naming conflicts, all official Hyperspace related modules are prefixed with hs_. So, for example, a kill spree module becomes hs_spree. This is not required for module submissions. You are free to name your module whatever you wish.

== Style ==

There is a Hyperspace standard style for formatting code, but it is completely optional. You should make your interface headers easy to read, though.

Here is an example of the Hyperspace official style:

''hs_twowords.h'':
<pre>
#ifndef HS_TWOWORDS_H
#define HS_TWOWORDS_H

#define I_HS_TWOWORDS "hs_twowords-1"

typedef struct Ihstwowords
{
INTERFACE_HEAD_DECL

int (*interfaceFunction)(Player *p);
} Ihstwowords;

#endif //HS_TWOWORDS_H
</pre>

''hs_twowords.c'':
<pre>
#include <string.h> //optional. others added as needed

#include "asss.h"
#include "hscore.h"
#include "hs_twowords.h"

//modules
local Imodman *mm;
local Ilogman *lm;
local Ichat *chat;
local Iconfig *cfg;
local Icmdman *cmd;
local Iplayerdata *pd;

//interface prototypes
local int interfaceFunction(Player *p);

local helptext_t twoWordsHelp =
"Targets: player\n"
"Args: none\n"
"Who knows? This is just a template file.\n";

local void twoWordsCommand(const char *command, const char *params, Player *p, const Target *target)
{
if (target->type == T_PLAYER) //private command
{
Player *t = target->u.p;

//do something
}
else //not private
{
chat->SendMessage(p, "You must target a player.");
}
}

local int interfaceFunction(Player *p)
{
if (something) //space between if and ()
{
//do something
}
}

local Ihstwowords interface =
{
INTERFACE_HEAD_INIT(I_HS_TWOWORDS, "hs_twowords")
interfaceFunction
};

EXPORT int MM_hs_twowords(int action, Imodman *_mm, Arena *arena)
{
if (action == MM_LOAD)
{
mm = _mm;

lm = mm->GetInterface(I_LOGMAN, ALLARENAS);
chat = mm->GetInterface(I_CHAT, ALLARENAS);
cfg = mm->GetInterface(I_CONFIG, ALLARENAS);
cmd = mm->GetInterface(I_CMDMAN, ALLARENAS);
pd = mm->GetInterface(I_PLAYERDATA, ALLARENAS);

if (!lm || !chat || !cfg || !cmd || !pd)
{
mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(cfg);
mm->ReleaseInterface(cmd);
mm->ReleaseInterface(pd);

return MM_FAIL;
}

mm->RegInterface(&interface, ALLARENAS);

cmd->AddCommand("twowords", twoWordsCommand, ALLARENAS, twoWordsHelp);

return MM_OK;
}
else if (action == MM_UNLOAD)
{
if (mm->UnregInterface(&interface, ALLARENAS))
{
return MM_FAIL;
}

cmd->RemoveCommand("twowords", twoWordsCommand, ALLARENAS);

mm->ReleaseInterface(lm);
mm->ReleaseInterface(chat);
mm->ReleaseInterface(cfg);
mm->ReleaseInterface(cmd);
mm->ReleaseInterface(pd);

return MM_OK;
}
return MM_FAIL;
}
</pre>

== Money and Experience ==

Money and experience points (aka exp) are what make the Hyperspace world go 'round. Nearly every Hyperspace module has some dealings with money/exp transactions of some kind.

Here is the '''hscore_money.h''' contents:

<pre>
#ifndef HSCORE_MONEY_H
#define HSCORE_MONEY_H

#define I_HSCORE_MONEY "hscore_money-1"

typedef enum MoneyType
{
//for /?give
MONEY_TYPE_GIVE = 0,

//for /?grant
MONEY_TYPE_GRANT,

//for ?buy and ?sell
MONEY_TYPE_BUYSELL,

//for money from kills
MONEY_TYPE_KILL,

//for money from flag games
MONEY_TYPE_FLAG,

//for money from soccer games
MONEY_TYPE_BALL,

//for money from module driven events
MONEY_TYPE_EVENT
} MoneyType;

#define MONEY_TYPE_COUNT 7

typedef struct Ihscoremoney
{
INTERFACE_HEAD_DECL

void (*giveMoney)(Player *p, int amount, MoneyType type);
void (*setMoney)(Player *p, int amount, MoneyType type); //beware. know what you're doing

int (*getMoney)(Player *p);
int (*getMoneyType)(Player *p, MoneyType type); //used only for /?money -d

void (*giveExp)(Player *p, int amount);
void (*setExp)(Player *p, int amount); //beware. know what you're doing

int (*getExp)(Player *p);
} Ihscoremoney;

#endif //HSCORE_MONEY_H
</pre>

=== Giving exp ===

<pre>
money->giveExp(p, 10); //gives player p 10 exp
</pre>

=== Giving money ===
The first thing to decide is which money type to give. This is mainly used for tracking purposes. If in doubt, choose '''MONEY_TYPE_EVENT'''.

*'''MONEY_TYPE_GIVE''' is for money moving from one player to another.
*'''MONEY_TYPE_GRANT''' is for money coming from a grant command
*'''MONEY_TYPE_BUYSELL''' is for ?buying and ?selling.
*'''MONEY_TYPE_KILL''' is for money gained from kills.
*'''MONEY_TYPE_FLAG''' is for money earned from winning flag games or other flag rewards.
*'''MONEY_TYPE_BALL''' is for money received from goals.
*'''MONEY_TYPE_EVENT''' is for subarena events.

Then you can simply call:
<pre>
money->giveMoney(p, 1000, MONEY_TYPE_EVENT); //gives player p $1000
</pre>

== Using Items ==

Items are the most important part of Hyperspace after money and exp. There are two parts of items that addon modules will use. These are checking for properties and calling events.

Here is a copy of ''hscore_item.h'':
<pre>
#ifndef HSCORE_ITEMS_H
#define HSCORE_ITEMS_H

#define I_HSCORE_ITEMS "hscore_items-3"

typedef struct Ihscoreitems
{
INTERFACE_HEAD_DECL

int (*getItemCount)(Player *p, Item *item, int ship);
void (*addItem)(Player *p, Item *item, int ship, int amount);

Item * (*getItemByName)(const char *name, Arena *arena);

int (*getPropertySum)(Player *p, int ship, const char *prop); //properties ARE case sensitive

void (*triggerEvent)(Player *p, int ship, const char *event);
void (*triggerEventOnItem)(Player *p, Item *item, int ship, const char *event);

int (*getFreeItemTypeSpots)(Player *p, ItemType *type, int ship);

//more required, i'm sure
} Ihscoreitems;

#endif //HSCORE_ITEMS_H
</pre>

=== Item properties ===

Most items define properties that are used to change the player's ship. Properties are totalled for each ship and are checked per ship rather than per item. Most properties are related to the spawning module. However, any item can define custom properties.

<pre>
item->getPropertySum(p, p->p_ship, "someproperty"); //Beware of spectators.
</pre>

=== Item events ===

Items define actions that happen on certain events. Any module can trigger an event. Some modules, for example, have actions on the ''death'' event. Triggering an event is as simple as making a function call to the '''hscore_item''' module. If no items have actions on the called event, nothing will happen (so make sure you don't typo the event name).

<pre>
item->triggerEvent(p, p->p_ship, "someevent"); //Beware of spectators.
</pre>

== Submission ==

Once your module is working properly and seems to have no bugs, then you can submit the source to Dr Brain or MichaelG for a source check. Once that's completed, the module will be compiled for the Hyperspace server and installed.

[[Category: Module]]
[[Category: Tutorial]]

Writing Modules for Hyperspace

2005-01-11T16:01:08Z

Dr Brain: /* Style */

Writing Modules for Hyperspace

2005-01-11T15:58:42Z

Dr Brain: /* Item events */ typo

Writing Modules for Hyperspace

2005-01-11T15:58:19Z

Dr Brain: Added some content. Still more to go.

Using Custom Modules

2005-01-11T15:35:34Z

Dr Brain:

Are people avoiding this page because you don't know what to put here? Is it going to be list of all publicly available custom modules and their documentation? --Smong

Yes. That was my impression. Module writers should make a link to a new page for thier module's setup/config/docs. --Dr Brain

----

To use a custom module you first need to install it, see [[Installing New Modules]].

Then you need to read the documentation that came with it so you know the settings and commands it uses.

[[Category: Module]]
[[Category: Tutorial]]

Writing Modules for Hyperspace

2005-01-11T14:01:16Z

Dr Brain: Added basic layout

I am editing. This may take a while. -- Dr Brain

== Getting Started ==

== Naming ==

== Style ==

== Money ==

== Items & Properties ==

== Submission ==

Writing Modules

2005-01-11T13:59:54Z

Dr Brain: Added writing modules for hyperspace

ASSS modules can be written in either C or Python.

C modules are best suited for large, complex modules that need direct access to the core features of ASSS.

The preferred language for simple modules is Python, because a poorly written module will not crash the entire server (Python is a safe language), while this is not the case for modules written in C.

*[[Writing Modules In C]]
*[[Writing Modules In Python]]
*[[Writing Modules for Hyperspace]] - Should this go somewhere else?

See also: [[Module Creation FAQ]]

[[Category: Module]]
[[Category: Tutorial]]

Writing Modules In C

2005-01-10T23:31:19Z

Dr Brain: /* Using Interfaces */ Changed mapdata to game, as that's what it is.

I'm editing this page right now... please don't change it till i'm done. I'll remove this when I finish. -Bak

The easiest way to write a module in C is to work off a template, as certain parts of all modules are identical. Here is a template that does nothing more than connect with the server:

== Template Module ==

<pre>
//Template Module

#include "asss.h"

// Interfaces
local Imodman *mm;

// The entry point:
EXPORT int MM_template(int action, Imodman *mm_, Arena *arena)
{
int rv = MM_FAIL; // return value

if (action == MM_LOAD)
{
mm = mm_;
rv = MM_OK;
}
else if (action == MM_UNLOAD)
{
rv = MM_OK;
}
else if (action == MM_ATTACH)
{
rv = MM_OK;
}
else if (action == MM_DETACH)
{
rv = MM_OK;
}

return rv;
}
</pre>

This modules loading function is called MM_template, and it is to be saved int template.c. This will make our module name be template when we are interested in loading it into a server. This is a good place to make sure that your module compiles, and that it loads into a server.

== Using Interfaces ==
Interfaces are your way of interacting with what happens in the game. Want to send a chat message to a player? You need an chat interface. Want to warp a player to (512,512)? You need a game interface. Want to toggle a lvz object? You get the idea...

The first thing you need to do is add your interface as a global like variable (We already have one interface, the module manager). Let's make a chat interface, so we can send chat text for the rest of this tutorial. Let's add our interface definition in our interfaces section:

<pre>
// Interfaces
local Imodman *mm;
local Ichat *chat;
</pre>

Now that we have a place to store the interface, let's get the interface. This is done when our function is loading, in the MM_template function. Here's the new MM_template function:

<pre>
// The entry point:
EXPORT int MM_template(int action, Imodman *mm_, Arena *arena)
{
int rv = MM_FAIL; // return value

if (action == MM_LOAD)
{
mm = mm_;

chat = mm->GetInterface(I_CHAT,ALLARENAS);

if (!chat) // check interfaces
rv = MM_FAIL;
else
rv = MM_OK;
}
else if (action == MM_UNLOAD)
{
mm->ReleaseInterface(chat);
rv = MM_OK;
}
else if (action == MM_ATTACH)
{
rv = MM_OK;
}
else if (action == MM_DETACH)
{
rv = MM_OK;
}

return rv;
}
</pre>

Here you can see use getting the interface from the module manager, checking if we actually got it (some servers chose to omit certain modules, so you could actually make a server without chat). You must also release the interface when the module unloads. If your module prevents the server from loading, chances are an interface it is using isn't loaded.

You can see exactly what each interface does, and what functions are available by each interface by viewing the appropriate header file. In chat.h we see the defintion for Ichat, which includes a function pointer to a function we'll use:

</pre>
// Send a green arena message to a player.
void (*SendMessage)(Player *p, const char *format, ...)
ATTR_FORMAT(printf, 2, 3);
</pre>

Okay, so where do we send this message? We can't really put it anywhere, since the only place our code has control is when the module is loading or unloading. We want to be able to do something like send the player a message whenever they change ships, or enter an [[ASSS Region]]. For something like this we need a callback.

== Listening For Callbacks ==
Callbacks are your way of listening for events. These include, a player entering an arena, changing ship, entering / exiting an [[ASSS Region]]. We'll handle a simple one, players changing ships. Whenever a player changes their ship we will message them that they changed ships (using our Ichat interface). Each callback has a callback function, which will be called when an event occurs. We pass a pointer to this function when we declare our callback. Here's the new code:

<pre>
// Interfaces
local Imodman *mm;

// Functions
local void ShipChange(Player *p,int ship, int newfreq)
{
chat->SendMessage(p,"You have changed ships.");
}

// The entry point:<br>
EXPORT int MM_template(int action, Imodman *mm_, Arena *arena)<br>
{
int rv = MM_FAIL; // return value

if (action == MM_LOAD)
{
mm = mm_;

chat = mm->GetInterface(I_CHAT,ALLARENAS);

if (!chat) // check interfaces
rv = MM_FAIL;
else
{
m->RegCallback(CB_SHIPCHANGE, ShipChange, ALLARENAS);
rv = MM_OK;
}
}
else if (action == MM_UNLOAD)
{
mm->UnregCallback(CB_SHIPCHANGE, ShipChange, ALLARENAS);
mm->ReleaseInterface(chat);
rv = MM_OK;
}
else if (action == MM_ATTACH)
{
rv = MM_OK;
}
else if (action == MM_DETACH)
{
rv = MM_OK;
}

return rv;
}

</pre>

To get the function definition for your callback, you only have to look in the appropriate header file.

== Iterating Through Every Player / Every Arena ==

== Declaring Arena / Player Data ==

== Adding Timers ==

== Adding Commands ==

Module Creation FAQ

2005-01-10T23:24:39Z

Dr Brain: removed editing 'lock'

== What module and function do I use to send messages to players? ==

The chat interface, '''Ichat''', is defined in ''chat.h'' and is used to send messages of all kinds.

Most of the chat interface functions use printf like syntax in their strings.

NOTE: You must get the '''I_CHAT''' interface from the ASSS Module Manager before using it, just like you must on every other interface.

To send a green message to a single player, you should use code similar to one of the following:

<pre>
chat->SendMessage(p, "This is a message");
chat->SendMessage(p, "This is a message that displays an int. %i", someInt);
chat->SendMessage(p, "This is a message that displays a char array. %s", charArray);
</pre>

To send a message to an entire arena, one should use code similar to one of the following:

<pre>
chat->SendArenaMessage(p, "This is an arena-wide message");
chat->SendArenaMessage(p, "This is an arena-wide message that displays an int. %i", someInt);
chat->SendArenaMessage(p, "This is an arena-wide message that displays a char array. %s", charArray);
</pre>

== How do I log events? ==

The log manager's interface, '''Ilogman''', is defined in ''logman.h'' and aids in debugging and notifying zone staff of unusual activity.

There are three log functions that are defined. '''Log''', '''LogP''' and '''LogA'''. All three have printf like syntaxes (just like the chat interfaces's functions) for easy addition of variable values to add in debugging.

There are five log levels that can be used when calling a log function.

<ul>
<li>'''L_DRIVEL''' is for meaningless log entries. Things that no sysop will ever care about. Use this level for printing out statements to help in debugging.</li>
<li>'''L_INFO''' is for things that people might care about.</li>
<li>'''L_MALICIOUS''' is for events that shouldn't happen unless someone is trying to hack/cheat. This is sent to online sysops as soon as it is logged (under default settings).</li>
<li>'''L_WARN''' is for things that probably shouldn't happen, but don't make a big difference.</li>
<li>'''L_ERROR''' is for events that are really bad. It is sent to online sysops as soon as it is logged (under default settings).</li>
</ul>

'''LogP''' is the most commonly used logging function. It should be used when you have access to a player pointer and the event relates to that player's actions.

<pre>
lm->LogP(L_DRIVEL, "my_module_name", p, "A log message attached to Player *p");
</pre>

'''LogA''' is attached to an arena rather than a player. This should be used whenever an event happens inside an arena but is tied to no specific player.

<pre>
lm->LogA(L_DRIVEL, "my_module_name", arena, "A log message attached to Arena *arena");
</pre>

'''Log''' is attached to neither an arena nor a player.

<pre>
lm->Log(L_DRIVEL, "<my_module_name> A log message");
</pre>

== How do I warp a player somewhere? ==

The game interface, '''Igame''' defines the function '''WarpTo''' that takes a player, an x tile and a y tile.

<pre>
game->WarpTo(p, 512, 512); //will warp a player to the center of the map
</pre>

== How do I give a player prizes? ==

The game interface, '''Igame''' defines the function '''GivePrize''' that takes a '''Target''', a prize type and a prize count.

<pre>
Target t;
t.type = T_PLAYER;
t.u.p = p;

game->GivePrize(t, 21, 5); //give Player p 5 repels (prize #21)
</pre>

== How do I set a player's ship? ==

== How do I set a player's freq? ==

== How do I check when a player has entered a region? ==

[[ASSS Regions]]

Module Creation FAQ

2005-01-10T23:17:05Z

Dr Brain:

I'm still typing (as of 5:57 PM EST 01-10-05). I will remove this message when finished.

== What module and function do I use to send messages to players? ==

The chat interface, '''Ichat''', is defined in ''chat.h'' and is used to send messages of all kinds.

Most of the chat interface functions use printf like syntax in their strings.

NOTE: You must get the '''I_CHAT''' interface from the ASSS Module Manager before using it, just like you must on every other interface.

To send a green message to a single player, you should use code similar to one of the following:

<pre>
chat->SendMessage(p, "This is a message");
chat->SendMessage(p, "This is a message that displays an int. %i", someInt);
chat->SendMessage(p, "This is a message that displays a char array. %s", charArray);
</pre>

To send a message to an entire arena, one should use code similar to one of the following:

<pre>
chat->SendArenaMessage(p, "This is an arena-wide message");
chat->SendArenaMessage(p, "This is an arena-wide message that displays an int. %i", someInt);
chat->SendArenaMessage(p, "This is an arena-wide message that displays a char array. %s", charArray);
</pre>

== How do I log events? ==

The log manager's interface, '''Ilogman''', is defined in ''logman.h'' and aids in debugging and notifying zone staff of unusual activity.

There are three log functions that are defined. '''Log''', '''LogP''' and '''LogA'''. All three have printf like syntaxes (just like the chat interfaces's functions) for easy addition of variable values to add in debugging.

There are five log levels that can be used when calling a log function.

<ul>
<li>'''L_DRIVEL''' is for meaningless log entries. Things that no sysop will ever care about. Use this level for printing out statements to help in debugging.</li>
<li>'''L_INFO''' is for things that people might care about.</li>
<li>'''L_MALICIOUS''' is for events that shouldn't happen unless someone is trying to hack/cheat. This is sent to online sysops as soon as it is logged (under default settings).</li>
<li>'''L_WARN''' is for things that probably shouldn't happen, but don't make a big difference.</li>
<li>'''L_ERROR''' is for events that are really bad. It is sent to online sysops as soon as it is logged (under default settings).</li>
</ul>

'''LogP''' is the most commonly used logging function. It should be used when you have access to a player pointer and the event relates to that player's actions.

<pre>
lm->LogP(L_DRIVEL, "my_module_name", p, "A log message attached to Player *p");
</pre>

'''LogA''' is attached to an arena rather than a player. This should be used whenever an event happens inside an arena but is tied to no specific player.

<pre>
lm->LogA(L_DRIVEL, "my_module_name", arena, "A log message attached to Arena *arena");
</pre>

'''Log''' is attached to neither an arena nor a player.

<pre>
lm->Log(L_DRIVEL, "<my_module_name> A log message");
</pre>

== How do I warp a player somewhere? ==

The game interface, '''Igame''' defines the function '''WarpTo''' that takes a player, an x tile and a y tile.

<pre>
game->WarpTo(p, 512, 512); //will warp a player to the center of the map
</pre>

== How do I give a player prizes? ==

The game interface, '''Igame''' defines the function '''GivePrize''' that takes a '''Target''', a prize type and a prize count.

<pre>
Target t;
t.type = T_PLAYER;
t.u.p = p;

game->GivePrize(t, 21, 5); //give Player p 5 repels (prize #21)
</pre>

== How do I set a player's ship? ==

== How do I set a player's freq? ==

== How do I check when a player has entered a region? ==

Module Creation FAQ

2005-01-10T22:56:08Z

Dr Brain: Initial Creation

Writing Modules

2005-01-10T22:35:47Z

Dr Brain:

ASSS modules can be written in either C or Python.

C modules are best suited for large, complex modules that need direct access to the core features of ASSS.

The preferred language for simple modules is Python, because a poorly written module will not crash the entire server (Python is a safe language), while this is not the case for modules written in C.

[[Writing Modules In C]]

[[Writing Modules In Python]]

[[Module Creation FAQ]]

Powerbot

2005-01-10T22:33:31Z

Dr Brain:

Powerbot is a bot core written by Mr Ekted in C. It is not open source, but is fast and does not use much memory. Rival bot cores include [[TWCore]] and [[MERVCore]].

User:Mine GO BOOM

2005-01-10T20:28:58Z

Dr Brain:

MGB: Supreme ruler of Server Help and all that passes within its sphere of influence.

MGB and his brother Shanky host shanky.com, minegoboom.com and a handful of other sites.

Best known for his work in maintaining the [http://www.shanky.com/server server help site] and the [http://forums.minegoboom.com link server help forum].

User:Dr Brain

2005-01-10T20:23:11Z

Dr Brain:

This is a page about Dr Brain.

Who am I? I am the owner and head honcho of SSCX-A Hyperspace. I do all the programming and settings work for the main arena. I also try my hand at mapping from time to time.

I've been working with ASSS since its first public release. I also spearheaded the move to ASSS for Hyperspace, making it the first playable ASSS zone.

I've written nearly all of Hyperspace's custom modules.

Server Setup

2005-01-10T20:05:25Z

Dr Brain:

This page needs a lot :)

Using Custom Modules

2005-01-10T20:05:00Z

Dr Brain:

This page could link to howtos written by custom module programmers.

Writing Modules

2005-01-10T20:03:11Z

Dr Brain:

Writing Modules

2005-01-10T20:03:00Z

Dr Brain:

Server Admin Tasks

2005-01-10T19:57:22Z

Dr Brain:

[[Using ?putfile, ?getfile and ?putzip]]

[[Creating New Subarenas]]

[[Installing New Modules]]