• ConfiguringTheGreatZero

Great Zero

Enabling all the markers

1. You will find markers in the next ages: BaronCityOffice, city, GreatZero, and Neighborhood.

2. Be sure that all GZMarkerVis, BOOL variables are enabled.

Great Zero SDL Variables

Marker Locations

These are the marker locations and the bit fields associated with them (set to 2 to for "found" and 1 for not found) for the GZMarkersAcquired Chronicle.

Quick, ugly fix for the GreatZero missing link at Nexus

Well, the server nicely deletes un-owned ages, or void ages.

The problem is simple; each time the GZ age is void the server deletes it. This causes the link for the GreatZero to disappear from the Nexus. The link appears again as soon as another neighbor uploads the green markers.

How to solve this nasty problem?

Very simple, adding a owner to the GreatZero's AgeOwnersFolder.

1. Subscribe to a player, that has access to the GZ, (is better if it is now at the GZ)

2. Locate the Neighborhood InfoNode.

3. You will see a "ChildAgesFolder" folder inside that node.

4. That folder should contain a link to the GreatZero, If you can't see it, be sure that a player is now in GZ.

5. 1st Rule, the Age Link node must contain these spawn points:

   Default:LinkInPointDefault:;Great Zero:BigRoomLinkInPoint:;

   If you can't see the second spawn point, then the link to the GZ is missing in the nexus.

6. Now, you need to add an owner to the GZ age, select the AgeOwnersFolder inside the GreatZero "Age Info Node".

7. Right click over that folder, and select "Add Child Node". Enter the id of a player(Info) listed in the "AllPlayers" folder. Important, if that player is deleted, the server cleaning script will delete the GZ instance again. Make sure you enter the id of the <player>(Info) node, not the player id itself. This means that you should take the field "ID" in the node mentioned above. If you do add the player ID itself as a child node, you may corrupt your vault, to the point that the vault server will crash! At that point, your shard is not working.

If you did accidentally enter a player node, and crashed your vault, you will need to follow the FixingCorruptVault directions.

Not so ugly temporary fix for the GreatZero missing link at nexus

Sometimes the ugly fix can corrupt the vault, even if you follow the steps above correctly. If you don't want to endanger your shard there is an alternative temporary fix.

1. Subscribe to a player, that has access to the GZ Observation

2. Locate the Neighborhood InfoNode.

3. You will see a "ChildAgesFolder" folder inside that node.

4. That folder should contain a link to the GreatZero, If you can't see it, be sure that a player is now in GZ Observation.

5. Note that the Age Link node contains this spawn point:

   Default:LinkInPointDefault:;

6. Change the spawn point to:

   Default:LinkInPointDefault:;Great Zero:BigRoomLinkInPoint:;

Now every member of the neighborhood of the subscribed player has the GZ link in the nexus. It will be deleted at the next server cleaning round, and you will have to apply this fix again.

Tip: If you subscribe to all Neighborhood InfoNodes of your shard, you can easily monitor whenever a player links into the GZ Observation. In that case you will see the link to the GreatZero appearing in the "ChildAgesFolder" of that Neighborhood InfoNode. You can then do the fix from step 6)

Note: this temporary fix will be really lightning speed temporary if you enabled auto-cleaning parameters (PeriodicDbCleanup=1) in your PlasmaServers.ini. (cleaning will happen every 2 seconds...). So 'ugly' fix is perhaps better (didn't have a single problem with ugly fix yet).

submitted by D'Lanor
note by KhouFou

Automatic GZ fix

See ServerScripts pages, look for 'fixgz' script and prerequisites. Usage: fixgz avatar_name. Script will fix GZ for this user using 'ugly' fix method. It will add GZ link into associated player's neighborhood.

Adding a Message into the GreatZero imager

Do exactly the same steps explained in PostingAtTheDRCImager page.

This time, you need to edit the grtzGZImagerInbox SDL var.

But this time is a little more complicated. You need to locate the AgeVmgrNode.

1. First, be sure that at least a player is now in the GreatZero.

2. To locate the AgeVmgrNode node run this SQL query in your vault db:

   SELECT UInt32_1 from Nodes where NodeType=33 and String64_1="GreatZero" and UInt32_1!=0

   You will see a list of GreatZero instances for each hood.

3. Subscribe to one of that instances.

4. Repeat the same steps explained at page PostingAtTheDRCImager

Caveat 1: Images are not working*.

Caveat 2: The server cleaning script will delete this age instance, if you don't add an owner to it.

*UPDATE: An accepted safe size is 500x375 (but it seems that 500x500 should work as well). You have to edit the images before uploading them as they are squeezed and brightened by the imager.