Elanthipedia - User contributions [en]

Currency

2019-08-21T22:04:26Z

HAZADO22: Dokoras to kronar exchange rate was wrong

{{incomplete|Needs premium banks listed out}}
{{RTOC}}
There are three types of '''currency''' in [[Elanthia]]: Kronar, Lirum, and Dokora, as well as one obsolete currency called the Dira.

==Currency Types==
Each province uses one currency type for all official and shop transactions.

===Kronars===
Kronars are used in the province of [[Zoluren]], and are the only coin accepted at [[vault]]s regardless of location.

The KRONAR is a round coin, with no edges. The circumference of the coin slopes downward, giving the edge of the entire coin a sharp, almost weapon-like look to it. On one side, a minuscule map of the contiguous landmass with the words ZOHLU REN underneath. The reverse shows the broad, patient face of an ox - symbolizing Elanthia as Truffenyi's planet.

===Lirums===
Lirums are used in the provinces of [[Therengia]] and [[Qi'Reshalia]].

Named after [[Lirum (person)|Lirum]], the wife of [[Akroeg]].

Shaped like a diamond with rounded edges, the LIRUM is the only coin of Elanthia to feature the likeness of a person. Along the corners on both sides of the coin, tiny roses have been stamped. One side features a stoic looking human woman with her hair in a bun. Centered under the portrait is the name LIRUM. On the reverse side, a simple seven-pointed star is situated in the middle with the words FEAS, KHALOR, HALEEN around the coin.

===Dokoras===
Dokoras are the coin of the realm in [[Ilithi]] and [[Forfedhdar]].

Oblong in shape, the DOKORA is the heaviest of the Elanthian currencies because of the weighted raised edges it possesses. These weighted edges exist to counterbalance a square hole in the middle of each DOKORA. The origins of the DOKORA are in Ilithi, although the coin is used elsewhere, and so one side shows two lotus blooms flanking the square hole, while the other side depicts a single cloud above and the words "Ylosh Sampul" below.

==Denominations==
{| class="wikitable" style="text-align:center"
|-
! Coin !! Copper !! Bronze !! Silver !! Gold !! Platinum
|-
| align="left" | '''Copper''' || '''1''' || 1/10 || 1/100 || 1/1,000 || 1/10,000
|-
| align="left" | '''Bronze''' || 10 || '''1''' || 1/10 || 1/100 || 1/1,000
|-
| align="left" | '''Silver''' || 100 || 10 || '''1''' || 1/10 || 1/100
|-
| align="left" | '''Gold''' || 1,000 || 100 || 10 || '''1''' || 1/10
|-
| align="left" | '''Platinum''' || 10,000 || 1,000 || 100 || 10 || '''1'''
|}

==Exchange Rates==
{| class="wikitable" style="text-align:center"
|-
! Currency !! Kronar !! Lirum !! Dokoras
|-
| align="left" | '''Kronar''' || '''1''' || 0.800 || 0.7216
|-
| align="left" | '''Lirum''' || 1.250 || '''1''' || 0.902
|-
| align="left" | '''Dokoras''' || 1.385808991 || 1.108646953 || '''1'''
|}
For example, 1000 Lirums is equivalent to 1250 Kronars or to 902 Dokoras.

[[Estate Holder]]s may use their [[bank book]]s to calculate exchange rates while in-game.

==Banks and Exchange Fees==
'''IMPORTANT NOTE ABOUT AMOUNT YOU MAY KEEP IN EACH INDIVIDUAL BANK BRANCH''' 
Attempting to put anything more than 212k platinum in any one bank may cause your account in that bank to rollover, that is -- cause your money to disappear. To prevent this, keep any money over this amount in other banks. 
 
Different Banks charge different fees for exchanging currency, ranging from 3%-13%. 
Money-changers in Elanthia will only handle transactions for 1,000 platinum and under.

{|class="wikitable sortable" style="text-align:center"
|+Sortable table
|-
!City!! Province!!Fee!!Notes
|-
|[[RanikMap1|Crossing]]||Zoluren||5%||
|-
|[[RanikMap1|Crossing (Strand Communal Center)]]||Zoluren||3%||Premium-only. Can withdraw from any bank.
|-
|[[RanikMap61|Leth Deriel]]||Zoluren||5%||
|-
|[[RanikMap13|Dirge]]||Zoluren||10%||
|-
|[[RanikMap112|Ilaya Taipa]]||Zoluren||10%||deposit-only bank that ties into Leth Deriel; charges a 7% fee
|-
|[[RanikMap42|Therenborough]]||Therengia||5%||
|-
|[[RanikMap30|Riverhaven]]||Therengia||7%|||
|-
|[[RanikMap30|Riverhaven (Armiger's Mansion)]]||Therengia||3%||Premium-only. Can withdraw from any bank.
|-
|[[RanikMap41|El Bain's Stop (Bank Under the Roots)]]||Therengia||3%|||Premium-only. Ties into Therenborough.
|-
|[[RanikMap35|Throne City]]||Therengia||7%||
|-
|[[RanikMap47|Muspar'i (foreigner)]]||Therengia||10%||
|-
|[[RanikMap47|Muspar'i (citizen)]]||Therengia||7%||
|-
|[[RanikMap34a|Rossman's Landing]]||Therengia||9%||ties into Riverhaven
|-
|[[RanikMap67|Shard]]||Ilithi||5%||
|-
|[[RanikMap150|Fang Cove]]||Ilithi||3%||Premium-only
|-
|[[RanikMap64a|Chyolvea Tayeu'a]]||Ilithi||8%||
|-
|[[RanikMap90|Ratha (1st Tier)]]||Qi'Reshalia||7%||
|-
|[[RanikMap90|Ratha (3rd Tier)]]||Qi'Reshalia||3%||Premium-only
|-
|[[RanikMap99|Aesry]]||Qi'Reshalia||9%||
|-
|[[RanikMap107|Mer'Kresh]]||Qi'Reshalia||9%||
|-
|[[RanikMap107|Mer'Kresh (Estate Holders Club)]]||Qi'Reshalia||3%||Premium-only.
|-
|[[RanikMap106|Hara'jaal]]||Qi'Reshalia||13%||
|-
|[[RanikMap117|Hibarnhvidar (Inner)]]||Forfedhdar||5%||same account as bank in Outer Hibarnhvidar
|-
|[[RanikMap116|Hibarnhvidar (Outer)]]||Forfedhdar||7%||same account as bank in Inner Hibarnhvidar
|-
|[[RanikMap117|Hibarnhvidar (Stoney Hub)]]||Forfedhdar||3%||Premium-only; ties into Hibarnhvidar
|-
|[[RanikMap121|Boar Clan]]||Forfedhdar||8%||Ranger- and Cleric-only; ties into Hibarnhvidar
|-
|[[RanikMap114|Ain Ghazal]]||Forfedhdar||9%||Premium-only; ties into Hibarnhvidar
|-
|[[RanikMap127|Raven's Point]]||Forfedhdar||9%||ties into Hibarnhvidar
|-
|First Arachnid Bank||Forfedhdar||5%||[[Hollow Eve Festival]] bank; ties into Hibarnhvidar
|}

==Notes==
Monetary coins are a special type of item. When held normally, they do not count against your total [[inventory]], but do have weight and will impact your [[encumbrance]] if carrying a large amount. They are also susceptible to [[Stealing|theft]].

Dropping coins will create coin items on the ground. Coins may be placed in and retrieved from [[moneybelt]]s to protect them from thieves.

==Non-Standard Currency==
Non-standard currencies are former or current forms of currency that are treated as items and not accepted as payment at most locations.

===Dira===
Dira were the currency of the [[Empire of the Seven-Pointed Star]], but are no longer valued as money. Instead, they are considered collector's items. See [[Dira]] for more information.

Each Emperor minted a coin of his or her predecessor, with their likeness and name along with the dates of rule. DIRA were minted in pure silver with high raised edges which was then surrounded by a thin band of the metal of the denomination of the DIRA. Much like present day currency, the DIRA came in copper, bronze, silver or gold. Platinum was not yet needed. Unfortunately, over the passage of time, the thin bands of these denomination markers have either worn off the coins or been removed, leaving most DIRA today as only the plain silver "internal" coin. ''Note: For reference, this means the coin was minted in silver, then an additional band of copper, bronze, silver, or gold was added to the outside to note the denomination.

===Oravir Slivers===
The [[vykathi]] of [[the Hive]] use {{Ilink|i|oravir sliver|slivers of oravir}} as some form of currency. While not used by any other race, some researchers are willing to exchange them for more common coins.

Oravir slivers are just that. They are not uniform in shape or size (although larger ones are not used or broken down into smaller slivers for storage purposes) and have no markings on them whatsoever.

==See Also==
*<tt>[[Protect command|PROTECT COIN]]</tt>
*[[Dira]]
*[[Currency Converter (script)]]: Genie script that converts between Elanthian currencies
*[[Currency Exchange Calculator (script)]]: Genie script that tells you how much money is needed to convert from one currency to another, including the exchange fee.

{{Cat|Concepts}}
[[page type is::concept| ]]

Item:Flash trinket (crafted)

2019-08-15T00:50:12Z

HAZADO22:

{{Item
|fname=No
}}
{{stub}}
{{CraftTemplate|itype=flash trinket|noun=<various>|type=misc|mat=sigil|dif=2|vol=1|matdetail=induction|tech=Basic Artificing Principles|||}}

This item will reflect the base component used to create it, so the base noun and measurements will vary. If the base component was ''a balsa cougar bead'', the finished item will also be ''a balsa cougar bead''.

==Focus==
An example {{com|focus}} for this item:
:You sense a matrix formed using Life mana, commonly referred to as the Flash Glamour Trinket enchantment.

:The enchantment appears of above-average quality, has great potency, demonstrates central complexity, and is abstract. This enchantment is of Lesser grade, and was modified to bonus durability. The matrix originally supported ''<number>'' charges, and has ''<number>'' charges remaining.
:You believe this item can be activated with rub.
==Standard==
''Use balsa wood as a base for reference.''

{|class="wikitable"
! Material !! Mat. Capacity !! Mat. Durability !! Speed !! Tool Durability !! Notes
|-
| Balsa|| 70 || 3 || - || - ||
|}

==Variations==
{|class="wikitable sortable"
! Material !! Mat. Capacity !! Mat. Durability !! Speed !! Tool Durability !! Notes
|-
| || || || || ||
|}

==Verbs==
* {{com|rub}}: You rub your thumb across the totem, causing your eyes to flash with a powerful blue light!

{{RefAl|p=-|a=y}}

Empathic shock

2019-08-12T23:24:53Z

HAZADO22: add message for max shock level

{{RTOC}}
'''Shock''' is the temporary loss of guild abilities that [[Empath]]s suffer when they perform violent acts. 

==Shock Theory==
Every sentient creature in [[Elanthia]] is born with innate empathy for the life forces of other living things. But for most, this sense is dulled and suppressed by a lifetime of the tiny (or not so tiny) harmful actions that are usually necessary for survival. Empaths, in contrast, strengthen and focus this natural sense into a highly refined sense, but to do so they must entirely avoid violence. 
 
When a non-Empath does harm, the suppression of natural empathy means they experience no ill effects. When an Empath attempts harm, it clashes violently with their finely-honed sensitivity to the life forces around them and causes shock. 
 
Contrary to popular belief, shock is not a punishment for breaching a moral code of pacifism. Rather, it is an automatic physiological reaction. Borrowing a player's analogy, Salvur made the following comparison: 
 
<blockquote>If you dwelt in a cave for a year and a day, and then wandered out into the noonday sun, the bright light would hurt your eyes, and you would be temporarily blinded. This is much like Empathic shock, which is pain followed by a temporary insensitivity that is caused by over-stimulation of one's empathic senses.</blockquote> 
 
There is no inherent moral component to shock, although many Empaths view shock as a highly personal issue and will only discuss it with their closest friends and family. 
 
'''SimuCon 2003 Empath Guild Seminar''': Why can an Empath not hunt, or not swing a sword without getting shock even if they don't actually hit anything? (Note: this is partially obsolete, as you must actually cause injury to experience empathic shock; intent is irrelevant.) 
 
When people are born today, over many generations, people have been developing the skill that will be empathy. As that power/ability developed, the suppression of it also developed. Everyone is capable of becoming an Empath. Those who make the choice to be combat oriented learn to suppress empathy. Empathy and the suppression of empathy are reflexive mental actions. When someone joins the Empath guild, suppression is not developed much if at all, but the empathy instinct is primed. The skill for suppression is suppressed and empathy is enhanced when a person joins the guild. Empathic shock is something done to the self when the suppression is suddenly activated to the empathy part of the brain. It is the natural suppression reflex which has been suppressed kicking in and kicking hard.

==Causes of Shock==

Empathic shock is primarily caused by directly harming living beings. Examples of actions that cause shock:
*injuring another creature or adventurer with weapons or damaging magic (as opposed to an unsuccessful attempt)
*fishing
*healing a [[Necromancer]] with sufficient [[Divine Outrage]]

The only surefire way to avoid empathic shock is to never attempt a shock-causing action. 
 
Shock will not happen when an Empath causes ''indirect'' harm, for example by hiring an assassin or firing a mangonel at a boat. Generally speaking, shock-causing actions require the Empath to be the '''primary, direct, and deliberate causative agent''' of harm. In the case of mangonels, the Empath is absolved since the direct target is an inanimate object (the boat) and not a living being. Finding a way to directly harm other characters without receiving shock is warnable as [[mechanics abuse]], and shock may be applied retroactively by a GM. 
 
Shock wears off with time as long as you are not "perma-shocked" or completely insensitive, but its duration can be considerable. Generally speaking, the more harm that was caused, the longer the length of shock. Merely punching or kicking someone will incur only perhaps an hour or two of shock, but it might take many days of being logged in for your empathy to recover from murder. Once you reach "perma-shock" or complete insensitivity, the [[Shock Quest|quest]] must be performed to jump-start the recovery process. The details of the quest are an in-game secret, so try discreetly asking other Empaths.

==Shock Levels==
Empaths can use a cassava root to determine their shock levels by {{tt|TOUCH}}ing it.
* Your [item]'s life force is brimming with unblemished vigor!
* Your [item]'s life force remains unblemished save for a single, tiny deadened speck.
* Your [item]'s life force remains largely robust, though several small deadened areas have formed.
* Your [item]'s life force is still mostly strong, though it shows more than the occasional deadened area.
* Your [item]'s life force displays interwoven strands connecting each of the deadened areas within.
* Your [item]'s life force is pulsing between vigor and numbness.
* Your [item]'s life force is waning, the strands connecting its deadened areas growing more numerous.
* Your [item]'s life force is significantly weakened, with large portions of it numbed and deadened completely.
* Your [item]'s life force is imperceptible.
* You thumb your [item].

==Consequences of Shock==
The first consequence of getting shock is a short stun. Empaths who have significantly deadened their Empathic sensitivity will have significantly shorter stuns than more sensitive Empaths. That is, the more shocked you are, the shorter your shock stun will be. Shock is granular, and as you accrue more shock, you will gradually weaken many of your abilities, and your effective skill with empathy may be penalized. For example, a partially shocked Empath will cast self-healing spells with less efficiency, and will not be able to perceive life as far as an unshocked Empath of equal skill. When you reach complete insensitivity ("perma-shock"), many of your abilities will not work at all or will only function at reduced power.<ref>[[Post:Shock Rewrite - 07/21/2012 - 21:22]]</ref> 
:'''The amount of shock an empath has will automatically drain as long as the Empath is both online and not currently permashocked/completely insensitive.''' If the Empath is completely insensitive the [[Shock Quest Walkthrough|shock quest]] must be performed to start the recovery process. The quest can also be performed before being completely insensitive to reduce recovery time.
The following abilities and spells will '''not work''' for the Empath who is completely insensitive ("perma-shocked"): 
*[[Empath Healing|healing others]]
*[[Link ability|link]]
*[[Perceive Health|perceive health]]
*[[Manipulate ability|manipulate]]
*[[Shift ability|shift]]
*[[Scholarship skill|teaching or listening to classes]] on empathy
*[[Fountain of Creation]]
*[[Guardian Spirit]]
*[[Heart Link]]
*[[Regenerate]]
*[[Circle of Sympathy]]
*Additionally, you will appear to be a non-Empath to Empaths who [[Perceive Health|perceive health]].
 
For playability reasons, the following "bread-and-butter" healing spells will still work but at '''reduced power/efficiency''': 
*[[Cure Disease]]
*[[Flush Poisons]]
*[[Heal Scars]]
*[[Heal Wounds]]
*[[Heal]]
 
These spells continue to work at full power while completely insensitive:
*[[Refresh]]
*[[Blood Staunching]]
*[[Vitality Healing]]
*[[Awaken]]
*[[Mental Focus]]
*[[Tranquility]]
*[[Compel]]
*[[Vigor]]
*[[Aggressive Stance]]
*[[Iron Constitution]]
*[[Paralysis]]
*[[Lethargy]]
*[[Aesandry Darlaeth]]
*[[Perseverance of Peri'el]]
*[[Gift of Life]]
*[[Innocence]]
*[[Nissa's Binding]]
 
Lastly, this spell cannot be learned or cast ''without'' a minimum amount of shock:
*[[Icutu Zaharenela]]
 
Empathic shock scars the Empath who first experienced it. Although the scar is permanent and perceptible (to other Empaths who touch you), there is no lingering mechanical effect once the shock wears off. '''You cannot get a scar by sharing shock from another Empath.''' 
 
; The creatures that spawn from the [[Ranger]] spell [[Awaken Forest]] are NOT constructs. Attacking them as an [[Empath]] WILL result in Empathic [[Shock]].

==Sharing Shock==
At 10th circle, other Empaths can {{tt|TAKE}} a portion of the shock to reduce the amount of time you are affected by it, but by doing so, they will become shocked themselves. Each time an Empath shares shock from a guildmate, he/she takes approximately half of the remaining shock, leaving half behind. '''Sharing shock from a guildmate does not cause stunning.''' 
 
The most efficient way to reduce shock is by organizing a '''Shock Circle'''. Since shock is reduced by half each time it is shared, you can benefit from this geometric reduction by setting up several tiers of Empaths to repeatedly take the shock in a hierarchical tree-like progression. A properly organized circle can quickly reduce shock since it will be worked off by many Empaths simultaneously. Shock circles are not easy to set up, since ideally you need five or more Empaths who are all willing to sacrifice their skills for several [[Elanthian Time|anlaen]] in order to help.

==Shock Quest==
Empaths also have the ability now to complete a lengthy quest to help reduce the time it takes to manage shock. A trip to the [[Adder's Coil]] in [[Forfedhdar]] will start the shocked Empath on the road to restoring their empathic senses. 
 
The following link contains spoilers about the quest:
* [[Shock Quest Walkthrough]]

{{RefAl}}
[[guild association is::Empath| ]]
[[page type is::definition| ]]

Item:Solid cambrinth bracer clasped with a rearing silver dragon

2019-07-24T06:16:28Z

HAZADO22:

{{Item
|name=a solid cambrinth bracer clasped with a rearing silver dragon
|noun=bracer
|look=Scorch marks mar the dragon clasp's formerly polished surface.
|MTag=metal
|type=cambrinth
|wearloc=upper arm
|weight=5
|appcost=18750
|sourcetype=-
|maxcharge=48
|fname=No
}}

Item:Miniature ruined keep carved from granite

2019-07-24T04:53:02Z

HAZADO22:

{{Item
|noun=keep
|look=This customization can be used with any normal freestanding home type home.

Example of what this customization could look like...

A nice freestanding home standing amidst a field of scattered rubble.

[To use this customization, PUT keep ON {HOME}.]
|appcost=125000
|sourcetype=-
|fname=No
}}

Item:Miniature ruined keep carved from granite

2019-07-24T04:52:41Z

HAZADO22: Created page with "{{Item |noun=keep |look=This customization can be used with any normal freestanding home type home. Example of what this customization could look like... A nice freestandi..."

{{Item
|noun=keep
|look=This customization can be used with any normal freestanding home type home.

Example of what this customization could look like...
A nice freestanding home standing amidst a field of scattered rubble.
[To use this customization, PUT keep ON {HOME}.]
|appcost=125000
|sourcetype=-
|fname=No
}}

Item:Miniature oak tree growing from within ruined walls

2019-07-24T04:49:57Z

HAZADO22:

{{Item
|noun=tree
|look=This customization can be used with any normal tree type home.

Example of what this customization could look like...
A nice tree growing among ruined granite walls.
[To use this customization, PUT tree ON {HOME}.]
|appcost=125000
|sourcetype=-
|fname=No
}}

Armor:Blackened steel gloves wrought with decorative scorched silversteel claws

2019-07-24T04:48:23Z

HAZADO22:

{{Armor
|newarmorapp=No
|noun=gloves
|look=Set at the end of each fingertip, the fire-blasted silversteel claws are a discreet but menacing addition to the overall design.
|type=chain armor
|area=hands
|hindrance=insignificant
|stealth=insignificant
|puncture=good
|punctureab=very great
|slice=very good
|sliceab=very great
|impact=good
|impactab=very great
|fire=moderate
|fireab=good
|cold=moderate
|coldab=good
|electric=low
|electricab=fair
|construction=highly protected
|metal=yes
|weight=48
|appcost=905625
|sourcetype=-
|fname=No
}}

Armor:Blackened steel gloves wrought with decorative scorched silversteel claws

2019-07-24T04:48:03Z

HAZADO22:

{{Armor
|newarmorapp=No
|noun=gloves
|look=Set at the end of each fingertip, the fire-blasted silversteel claws are a discreet but menacing addition to the overall design.
|type=chain armor
|hindrance=insignificant
|stealth=insignificant
|puncture=good
|punctureab=very great
|slice=very good
|sliceab=very great
|impact=good
|impactab=very great
|fire=moderate
|fireab=good
|cold=moderate
|coldab=good
|electric=low
|electricab=fair
|construction=highly protected
|metal=yes
|weight=48
|appcost=905625
|sourcetype=-
|fname=No
}}

Item:Length of dreamweave fabric

2019-07-24T04:46:29Z

HAZADO22:

{{Item
|noun=fabric
|look=The deep purple fabric has a subtle whorled appearance and displays slight variations in sheen across its surface when hit by light.
|MTag=dreamweave
|wearloc=head, chest, shoulders, legs
|sourcetype=-
|fname=No
}}
You study your dreamweave fabric. The rectangular piece of cloth is big enough to wrap around you in a variety of ways. You're sure you can TURN it to determine how it is worn, as well as FOLD and UNFOLD it to lengthen or shorten it.

Currently the fabric may be worn around your torso as a bandeau/sleeveless vest (folded) or dress/toga (unfolded).

Currently the fabric may be worn on your head as a turban (folded) or headdress (unfolded).

Currently the fabric may be worn over your shoulders as a shawl (folded) or cape (unfolded).

Currently the fabric may be worn around your hips as a short sarong or loincloth (folded) or a calf-length sarong (unfolded).

Item:Length of dreamweave fabric

2019-07-24T04:45:52Z

HAZADO22: Created page with "{{Item |noun=fabric |look=The deep purple fabric has a subtle whorled appearance and displays slight variations in sheen across its surface when hit by light. |MTag=dreamweave..."

{{Item
|noun=fabric
|look=The deep purple fabric has a subtle whorled appearance and displays slight variations in sheen across its surface when hit by light.
|MTag=dreamweave
|wearloc=head, chest, shoulders, legs
|sourcetype=-
|fname=No
}}
You study your dreamweave fabric. The rectangular piece of cloth is big enough to wrap around you in a variety of ways. You're sure you can TURN it to determine how it is worn, as well as FOLD and UNFOLD it to lengthen or shorten it.

Currently the fabric may be worn around your torso as a bandeau/sleeveless vest (folded) or dress/toga (unfolded).
Currently the fabric may be worn on your head as a turban (folded) or headdress (unfolded).
Currently the fabric may be worn over your shoulders as a shawl (folded) or cape (unfolded).
Currently the fabric may be worn around your hips as a short sarong or loincloth (folded) or a calf-length sarong (unfolded).

Lich mapping reference

2019-07-23T16:04:51Z

HAZADO22: Adding identical room mapping instructions

== Introduction to Mapping==
This guide is inspired by Tillmens posts on lrn2map: http://forum.gsplayers.com/showthread.php?57828-lrn2map (Note: ignore any mentions of mapmap, this script does not apply to Dragonrealms)

The map is a database that is downloaded to your lich directory each time you login to the game. The database consists of rooms. All rooms need to have a wayto and a timeto. A wayto describes the movement to get to the room. The timeto describes how long it takes to get there (0.2 seconds is the default). <code>;automap</code> handles adding this data automatically in most cases. If you map a room manually without <code>;automap</code> then you need to be sure that you include both the timeto and the wayto, forgetting one will break ;go2's ability to navigate to that room.

=== Updating Your Database ===
To fetch the latest version of the map database run these commands:
<pre>
;repository download-mapdb
;e Map.reload
</pre>

=== Checking out the Database ===

Check out the map database. This will replace your current map database with the remote. This means that any changes you have made will be erased! This does not include anything like <code>;go2</code> saved rooms.

You need to have a password on file to check out the mapdb. This password is stored in plain text locally, so don't make it anything important.

When you checkout the map db, you own the database for 24 hours. This means that no one else can check it out until you upload or release it. Please, for the love of god, don't forget this.

<pre>
> ;repository checkout-mapdb
[repository: success; running download-mapdb now...]
[repository: map database is up-to-date]
[repository: done]
[repository: edit your map database and ;repository upload-mapdb within 24 hours.]
--- Lich: repository has exited.
</pre>

=== I Screwed Up ===

If you don't have the map db checked out, but want to erase some local changes you made:

<pre>
;repository download-mapdb
</pre>

All changes are local until you upload the database. If you checked it out but didn't upload it, you can RELEASE it which will erase your changes since your checkout and allow others to check out the mapdb again.

<pre>
;repository release-mapdb
</pre>

=== Referencing Rooms ===
Rooms can be referenced in two ways: <code>Map.list[room_id]</code> or <code>Room[room_id]</code>. There are some idiosyncrasies between the two, but in most cases either will work fine.

<code>Room.current</code> refers to your current room.

<code>Map.list[room_id]</code> or <code>Room[room_id]</code> refers to any room with the given id

=== Re-routing a path by changing timeto ===
You can change a path if there is an obstacle that you want to avoid, like a wall that might be too difficult to climb for younger adventurers!
<pre>
;e Room.current.timeto["5665"] = 10.0
</pre>

=== Useful Aliases ===
If you are using the Dependency suite of scripts, please run <code>;setupaliases</code> to install these some of these useful mapping aliases. It will not install all of them, currently.
<pre>
;alias add lr = ;e echo Room[Room.current.id].inspect
;alias add lfr = ;e echo Room[\?].inspect
;alias add ad = ;e Room[\?].description.push(XMLData.room_description) # Usage: ad roomnumber
;alias add snip = ;e Room.current.timeto.delete("\?")\r;e Room.current.wayto.delete("\?"); # Usage: snip roomnumber
;alias add ids = ;e echo "#{Room.current.id}:#{Room.current.wayto}"
;alias add tag = ;e Room.current.tags.push("\?") # Add tag to current room, Usage: tag cleric
;alias add pop = ;e echo Room.current.tags.pop #deletes the last tag from the room you are in and displays it to you!
</pre>
Note: Genie users must use slight variations for these commands. For instance, a comma instead of a semicolon, and double backward slashes where there is a backward slash.
For example:
,alias add lfr = ,e echo Room[\\?\].inspect

=== Useful commands ===
<pre>
<nowiki>;e echo Room.current.inspect # This is the lr alias</nowiki>
<nowiki>;e echo Room.current.wayto</nowiki>
</pre>

=== When You Are Done ===

Run this command to merge your database with the server. Players that are logged in will not receive this update, they will have to execute the commands given above, or re-login to the game.
<pre>
;repository upload-mapdb
</pre>

== Common Mapping Techniques ==

=== Adding New Rooms ===
====Example====

In this room there's an archway that is unmapped. Using the <code>ids</code> alias, its shown as unmapped.
<pre>
[Inner Hibarnhvidar, Upper Cavern]
The generations of skilled Dwarven craftsmen that cleaved this cavern out of the living rock of the mountain let their imaginations run free in the carvings surrounding the arches leading to the shops and work-caverns. One is surrounded by flowing rock-hewn ribbons pleated in an intricate pattern, others are studded with cabochon gems or tiny carvings in minute detail. You also see a stone arch inscribed with the MAMAS Company logo.
Obvious exits: north, northeast, east, southeast.
Room Number: 3812
>ids
--- Lich: exec1 active.
[exec1: 3812:{"3815"=>"northeast", "3811"=>"north", "3813"=>"southeast", "3814"=>"east"}]
--- Lich: exec1 has exited.
</pre>
Walk through the arch to check the movement command and see if the room has an id (it doesn't).
<pre>
>go arch
[MAMAS Hibarnhvidar, Main Office]
Several small work stations ring the large cavern of the Merchant Adventurers' Mapping, Assay, and Survey Company's primary office in Forfedhdar. Tools and survey instruments lie stacked at the various stations, soon to be available for purchase by adventurers needing the latest in mining equipment. At the end of the cavern, a lone clerk stands by a counter with a set of small scales used to weigh individual items and stones of valuable minerals. You also see a sign.
Obvious exits: out.
>out
You stroll out.
[Inner Hibarnhvidar, Upper Cavern]
The generations of skilled Dwarven craftsmen that cleaved this cavern out of the living rock of the mountain let their imaginations run free in the carvings surrounding the arches leading to the shops and work-caverns. One is surrounded by flowing rock-hewn ribbons pleated in an intricate pattern, others are studded with cabochon gems or tiny carvings in minute detail. You also see a stone arch inscribed with the MAMAS Company logo.
Obvious exits: north, northeast, east, southeast.
Room Number: 3812
</pre>
Check out the map database
<pre>
>;repository checkout-mapdb
--- Lich: repository active.
[repository: success; running download-mapdb now...]
[repository: downloading map database...]
[repository: deleting old map databases...]
[repository: loading map database...]
[repository: done]
[repository: edit your map database and ;repository upload-mapdb within 12 hours.]
--- Lich: repository has exited.
</pre>
Run automap
<pre>
>;automap
--- Lich: automap active.
Starting
**Mapping (abort to cancel, stop to finish)**
Your feet are still soaked.
</pre>
Move through the path to be mapped and map the path back. Moving a direction does not map the reverse direction, you need to do the reverse direction as well. This means a room with 8 exits will need 16 steps, one forward, one backward. Wait for the "**Mapping" text before moving again. Using a typeahead line will not map the direction correctly.
<pre>
>go stone arch
[MAMAS Hibarnhvidar, Main Office]
Several small work stations ring the large cavern of the Merchant Adventurers' Mapping, Assay, and Survey Company's primary office in Forfedhdar. Tools and survey instruments lie stacked at the various stations, soon to be available for purchase by adventurers needing the latest in mining equipment. At the end of the cavern, a lone clerk stands by a counter with a set of small scales used to weigh individual items and stones of valuable minerals. You also see a sign.
Obvious exits: out.
**Mapping (abort to cancel, stop to finish)**
>out
You stroll out.
[Inner Hibarnhvidar, Upper Cavern]
The generations of skilled Dwarven craftsmen that cleaved this cavern out of the living rock of the mountain let their imaginations run free in the carvings surrounding the arches leading to the shops and work-caverns. One is surrounded by flowing rock-hewn ribbons pleated in an intricate pattern, others are studded with cabochon gems or tiny carvings in minute detail. You also see a stone arch inscribed with the MAMAS Company logo.
Obvious exits: north, northeast, east, southeast.
Room Number: 3812
**Mapping (abort to cancel, stop to finish)**
</pre>
Done mapping. Double check with the <code>ids</code> alias.
<pre>
>ids
--- Lich: exec1 active.
[exec1: 3812:{"3815"=>"northeast", "3811"=>"north", "3813"=>"southeast", "3814"=>"east", "12182"=>"go stone arch"}]
--- Lich: exec1 has exited.
</pre>
Kill automap
<pre>
>;k automap
--- Lich: automap has exited.
>go arch
[MAMAS Hibarnhvidar, Main Office]
Several small work stations ring the large cavern of the Merchant Adventurers' Mapping, Assay, and Survey Company's primary office in Forfedhdar. Tools and survey instruments lie stacked at the various stations, soon to be available for purchase by adventurers needing the latest in mining equipment. At the end of the cavern, a lone clerk stands by a counter with a set of small scales used to weigh individual items and stones of valuable minerals. You also see a sign.
Obvious exits: out.
Room Number: 12182
</pre>
Upload the map database with <code>;repository upload-mapdb</code>

=== Delete a room ===
Go to each surrounding room and perform the following, where "roomid" is the id of the room you are going to delete. It must be enclosed in quotation marks. This is the same as the 'snip' alias above.
<pre>
<nowiki>;e Room.current.wayto.delete("roomid")</nowiki>
<nowiki>;e Room.current.timeto.delete("roomid")</nowiki>
</pre>

Finally, remove the room. Roomid is NOT quoted here. Enter it as a number.
<pre>
<nowiki>;e Map.list[roomid] = nil</nowiki>
</pre>

=== Advanced Movements with StringProcs ===
Complicated actions ones which require multiple movements to get to the target room. A complex action is not just go, move, climb, etc... but involving searching to discover the path, or pushing an object to open a door. Use a stringproc to add these. Note: these actions require approval from the mapdb admin, and will lock the mapdatabase until they are approved/rejected. Do not add them without testing them.
<pre>
;e Room.current.wayto['1220'] = StringProc.new(“fput 'search'; move 'go path'”)
</pre>

==== Calling Bescort with StringProcs ====
Certain actions like navigating mazes and ferry crossings are more smoothly handled by a separate script. Rather than create a complicated StringProc, its preferred to use <code>bescort</code>. Modify <code>bescort.lic</code> to handle the navigation and then start it in the desired room using a StringProc.

Here is an example of a StringProc to call bescort to take the sea mammoth from Ratha to Fang Cove.
<pre>
StringProc.new("start_script('bescort', ['mammoth', 'fang']);wait_while{running?('bescort')};")
</pre>

It is also suggested that you get some sort of accurate estimate of the crossing time! Don't use the default 0.2 seconds for the timeto if it takes minutes. Timing impacts the route <code>go2</code> decides to take.

=== Update Rooms with multiple descriptions ===
Go2 uses room descriptions part of determining what room you're in. If the room has multiple descriptions, the room you are in may appear to be unmapped during some seasonal/time change. To correct this, add the room description to the correct room. Do not remap the room.

This assumes you are standing in the target room with its new description and you know the roomid. You can find the roomid by going to a connecting room and looking at the room number for the direction of the room without a number.

If you have not already, you need to run <pre><nowiki>;alias add ad = ;e Room[\?].description.push(XMLData.room_description)</nowiki></pre>
then
<pre>
<nowiki>;repository checkout-mapdb</nowiki>
<nowiki>ad roomnumber-it-should-be</nowiki>
<nowiki>;repository upload-mapdb</nowiki>
</pre>

==== Example ====
The first room in the log below doesn't have a room ID. This could either be unmapped or missing a description. To find out, we'll visit a neighboring room and check its exits using the 'ids' alias. If the exits point to the missing room then we know its room ID and just have to update the description. When we know the room ID we walk back and use the 'ad ####' alias to update the given roomid with the description of the room we are standing in. To verify it was updated, we re-enter the room and see that it now has a room id.

<pre>
[Boar Clan, Split-Log Path]
The sounds of the forest permeate the palisade wall and wash over the sleeping village. Each breath of wind rustles the trees that stir the night air and conduct the arboreal symphony. Chirping insects and the deep throaty calls of frogs keep the rhythm while high-pitched animal cries weave a soprano's song with a melody only nature could compose.
Obvious paths: northeast, west.
>ne
You stroll northeast.
[Boar Clan, Split-Log Path]
A tall palisade wall of thick iron-banded tree trunks embraces the small village of thatched longhouses and bark-covered huts. Split log walkways snake between the structures. One rutted dirt path leads from the gate to a squarish building with deep eaves that shelters stacks of crates and barrels piled outside the door. You also see a palisade gate, the stable doors and a long log nestled underneath a nearby tree.
Obvious paths: northeast, southwest.
Room Number: 4106
>;repo checkout-mapdb
--- Lich: repository active.
[repository: success; running download-mapdb now...]
[repository: map database is up-to-date]
[repository: done]
[repository: edit your map database and ;repository upload-mapdb within 24 hours.]
--- Lich: repository has exited.
>ids
--- Lich: exec1 active.
[exec1: 4106:{"4105"=>"go gate", "4107"=>"southwest", "4109"=>"northeast"}]
--- Lich: exec1 has exited.
>sw
You stroll southwest.
[Boar Clan, Split-Log Path]
The sounds of the forest permeate the palisade wall and wash over the sleeping village. Each breath of wind rustles the trees that stir the night air and conduct the arboreal symphony. Chirping insects and the deep throaty calls of frogs keep the rhythm while high-pitched animal cries weave a soprano's song with a melody only nature could compose.
Obvious paths: northeast, west.
>
Your body below the waist is dripping with water. Pools of it are forming all around you.
>
You've gained a new rank in your knowledge of sorcery.
>ad 4107
--- Lich: exec1 active.
--- Lich: exec1 has exited.
>ne
>sw
You stroll northeast.
[Boar Clan, Split-Log Path]
A tall palisade wall of thick iron-banded tree trunks embraces the small village of thatched longhouses and bark-covered huts. Split log walkways snake between the structures. One rutted dirt path leads from the gate to a squarish building with deep eaves that shelters stacks of crates and barrels piled outside the door. You also see a palisade gate, the stable doors and a long log nestled underneath a nearby tree.
Obvious paths: northeast, southwest.
Room Number: 4106
>
You stroll southwest.
[Boar Clan, Split-Log Path]
The sounds of the forest permeate the palisade wall and wash over the sleeping village. Each breath of wind rustles the trees that stir the night air and conduct the arboreal symphony. Chirping insects and the deep throaty calls of frogs keep the rhythm while high-pitched animal cries weave a soprano's song with a melody only nature could compose.
Obvious paths: northeast, west.
Room Number: 4107

</pre>
=== Adding identical rooms ===
Taken from [http://forum.gsplayers.com/showthread.php?57828-lrn2map&p=1826134#post1826134]

Fixing this sort of thing requires more knowledge of how the map database works than your standard mapping procedure. If it wasn't in River's Rest, I could run over to the room and give it a look and either fix it or give you some useful pointers, but since it's in River's Rest and I'm lazy, you're screwed.

My assumption is that there are two rooms that are in different places but have the same room title/description/paths. There are several ways to deal with this, and they are mostly terrible.

First, go to each of the identical rooms and type:

<pre>
;e echo Room.current_or_new
</pre>

If one of them shows up with a new room number, everything is good and right in the world (this isn't going to happen).

Second, perhaps someone used ";mapmap fix" incorrectly (they didn't, because no one uses that, even though it's in the instructions). To check if this is the case, go to each of the identical rooms and type:

<pre>
;e echo Room.current.desc.length
</pre>

In the map database, rooms can have more than one description. This is mostly to deal with different night/day descriptions for the same room, but it can rarely have other uses. When using ";mapmap fix", the script tests existing paths to see if you end up in the expected room. If you don't, it'll ask you if the rooms are the same. If you tell it they're the same, it'll combine them so they both have the same room number. If not, it will delete the path and create a new one to the different room. Someone may have said yes when they shouldn't have, which would add two unrelated room descriptions (and/or titles/paths) to the same room id. If the above command says "1", then this is not the case. If it's more than one, then it might be the case, but I won't go into it further because it's too unlikely.

So now we need to differentiate between the two horrible rooms. The best way to do this is with the room_objects tag. If there's something that shows up in the "You also see" line that is permanent, such as an arch or a door or something, and it's in one room but not the other, then all is good and right in the world (unlikely). Type:

<pre>
;e echo DRRoom.room_objs
</pre>

to see the exact object name, and then type:

<pre>
;e Room.current.room_objects = [ 'whatever' ]
</pre>

replacing whatever with the object name. Now, the room that has that object should keep the room number, and the room without the object should either be unknown, or might still tell you it knows the room id because of fuzzy room lookups. Either way, go to the other room and do a:

<pre>
;e echo Room.current_or_new
</pre>

and there should be two room ids. Then you can go over the whole area with a ";mapmap map" and a ";mapmap fix" and it should be good.

If room_objects isn't an option, you can use a peer tag, which causes Lich to peer into the next room in order to discriminate between two rooms. This is nice because it lets you use either room as a target for go2, but it's terrible because it has to peer if you walk through the room with narost running.

If the title/description/paths of each adjacent room is identical in each identical room (unlikely but actually has happened more than once), then you're stuck with treating the two rooms as one. You would need to create some creative StringProcs paths from each room to each adjacent room that will be sucessful regardless of which of identical room it's started in.

I left out the location verb property because it sounds like these rooms are in the same location.

=== Adding a new map image ===
Lets add a new map image!

Copied from lrn2map:

Step 6: Add to narost (if needed or wanted)

6a. Add the image to the map database. Narost will only display images that are already in the map database. If the image is already in the map database because it's used by other rooms, move on to 6b. If not, save the image in the lich\maps directory, go to a room that will use the image, and type ;e Room.current.image = 'filename' # substitute the actual filename of the image, including the file extension, but without the path. Name the file is all lowercase with the formatting province-mapnumber-name-timestamp.whatever. You can get the timestamp by typing date +%s in a linux environment. If you leave a timestamp off there is no way to overwrite the map with a newer version without uploading a new file name. Make absolutely sure not to include apostrophes in the name.

6b. Start narost in fix mode (;type ;narost fix)

6c. Bring up the image in narost. Right-click in the narost window, click on “view map” in the popup menu, and click on the image name that you'll be adding to.

6d. Move the image around to find where your current room goes.

6e. Hold down the Shift and Ctrl keys, click on the top left and bottom right corners of the room on the image, let go of Shift and Ctrl.

6f. If there are more rooms to add, move to the next room in game, go to step 6d.

6g. Save the map database (type ;e Map.save). While the mapmap script saves the map database every time it closes, narost does not. You can save the map database as often as you like if you are worried about losing your progress.

[[Category: Lich scripts]]

Lich script development

2019-07-13T03:37:31Z

HAZADO22: /* sorter */

{{RTOC}}

== Lich script libraries ==

These are lich scripts, but do not accomplish a task. Rather, they provide functionality that other scripts can take advantage of.

=== bootstrap ===
{{Lich script
|description=
|usage=You can turn on debug mode with <code>;e UserVars.bootstrap_debug = true</code>
|args=
|settings=
|uservars=
|children=
}}

=== common ===
{{Lich script
|description=A large set of helper functions for common actions shared by many scripts.
|usage=
Probably the single most useful function in this file is <code>bput</code> (short for 'blocking put').

bput is designed to be a more robust version of fput in situations where you know the desired response from the game. Unlike fput which will resend the same command repeatedly until it sees the desired message first from the game, bput only sends a given command one time (unless round time or type ahead errors occur) and then waits for the desired response. if the desired response isn't seen bput will eventually time out and echo debugging information.

This would never work because the game sends a response line "You search around..." before "Roundtime" is encountered:

<code>fput "forage grass", 'Roundtime'</code>

Similarly a command that can only succeed once can cause fput to hang. In this case, you have to deal with the failure case and just spam the command until failure in a noisy room with fput:

<code>fput "get box", 'you pick up', 'get what?'</code>

Lets you know with confidence if a box was picked up or if the item was missing:

<code>bput "get box", 'you pick up', 'get what?'</code>
|args=
|settings=
|uservars=
|children=
}}

=== common-arcana ===
{{Lich script
|description=A large set of helper functions for common actions related to spell casting, ability activation, etc.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-crafting ===
{{Lich script
|description=A large set of helper functions for common actions related to crafting.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-healing ===
{{Lich script
|description=A large set of helper functions for common actions related to health, wounds, and healing.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-items ===
{{Lich script
|description=A large set of helper functions for common actions related to manipulating items.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-money ===
{{Lich script
|description=A large set of helper functions for common actions related to money and coins.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-summoning ===
{{Lich script
|description=A large set of helper functions for common actions related to summoning weapons.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-travel ===
{{Lich script
|description=A large set of helper functions for common actions related to travel.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== dependency ===
{{Lich script
|description=
|usage=
For first time setup, see the Getting Started section of the repository README: https://github.com/rpherbig/dr-scripts/blob/master/README.md

You'll want to remove any of our scripts that you replace with this from the auto start so they aren't getting run twice.

Useful helpers:
* <code>get_script('name')</code> - fetch the script and start tracking it
* <code>get_yaml('filename')</code> - download the specified yaml file to your profiles directory
* <code>list_autostarts</code> - show all scripts that are started automatically
* <code>autostart(script)</code> - add a script to the autostart list
* <code>remove_autostart(script)</code> - remove a script from the autostart list
* <code>list_tracked_scripts</code>

You can turn on debug mode by passing 'debug' as an argument with <code>;dependency debug</code>
|args=
|settings=
|uservars=
|children=
}}

=== drinfomon ===
{{Lich script
|description=Updated info tracking for use in other scripts in DragonRealms
|usage=
* skill tracking - name/rank/xp
* info tracking - everything listed under info other than debt wealth and birthdate

Provides some additional commands to the user:
* <code>;banks</code> - Tracks your money and converts copper strings to plat format. Not all locations tracked.
* <code>;vault</code> - Tracks vault contents and location. -not all location included

Display experience gain in your Field Experience window:
* <code>;e UserVars.track_exp=true</code>
|args=
|settings=
|uservars=
|children=
}}

=== events ===
{{Lich script
|description=Flags are simple true/false string detectors.
|usage=
* <code><nowiki>Flags.add(<key>, <trigger>|[<trigger1,...,triggerN])</nowiki></code>
* <code><nowiki>Flags.add('test', 'exp help')</nowiki></code>
* <code><nowiki>Flags.add('another', ['exp help', 'a second message'])</nowiki></code>
This creates a new flag "test", which will return the matched string any time you see a message containing "exp help". Note that
the message will be treated as a regular expression and is case insensitive (google for more info) so be careful with
special characters, remember to use single quote strings if you're going to use special characters.
Calling add with the same key will overwrite any previous matchers and reset the flag.
Alternatively you can add an array with multiple matchers. If multiple messages match the flag will be set to the first match found.

* <code><nowiki>Flags.add('skillexp', '(\w[^:\(\)]+):\s+(\d+)\s\d+\.\d+%[^\(\)]*\((\d+)\/\d+\)')</nowiki></code>
This example will add a flag watching for the results of an exp message, specifically "exp skillname".
After sending "exp mech" to the game Flags['skillexp'] would contain...

["Mechanical Lore: 146 16.82% focused (20/34)", "Mechanical Lore", "146", "20"]

You can see the array containing entire matched string and the three capture groups containing
skill name, ranks, and mind state.

* <code><nowiki>Flags['test']</nowiki></code>
Returns the match if you've seen any message matching after you called add (or reset); false otherwise

* <code><nowiki>Flags['test'] = false</nowiki></code>
* <code><nowiki>Flags.reset('test')</nowiki></code>
Both of these commands have the same effect, reseting a flag as if it hasn't been seen yet.

* <code><nowiki>Flags.delete('test')</nowiki></code>
Removes a flag, stopping any tracking of it.
|args=
|settings=
|uservars=
|children=
}}

=== sorter ===
{{Lich script
|description=A script that converts inventories into sorted categories.
|usage=
|args=
|settings={{Lich setting|name=width|desc=<nowiki>(0-9999)</nowiki> Specify how many characters wide your game window is, and the script will display container contents in columns.}}^{{Lich setting|name=mute_old_inventory|desc=<nowiki>(True|False)</nowiki> Will mute the normal output for inventory, so you don't get sorted version and the normal output}}^{{Lich setting|name=sort_inv_command|desc=<nowiki>(True|False)</nowiki> Sorts the output from command "inventory"}}^{{Lich setting|name=sort_look_others|desc=<nowiki>(True|False)</nowiki> Sorts the output looking at other players}}^{{Lich setting|name=sort_look_items_command|desc=<nowiki>(True|False)</nowiki> Sorts the output from command "look item"}}^{{Lich setting|name=ignore_categories|desc=Categories from base-items.yaml to ignore. Enter in regex format. Default is <code><nowiki>lootables|trash</nowiki></code>}}
|uservars=
|children=
}}

===spellmonitor===
{{Lich script
|description=
|usage=
* <code>DRSpells.prep_spell</code> - returns the string name of the currently preparing spell or nil
* <code>DRSpells.active_spells</code> - returns hash of spells keyed to duration e.g. <code>{"Bless"=>5, "Minor Physical Protection"=>12}</code>
** 0 means fading, removed from the hash is worn off
|args=
|settings=
|uservars=
|children=
}}

== Development tools ==

=== create_symlinks.bat ===
Useful if you are doing development on Windows. Set the LICH_SCRIPTS environment variable to the path to your <code>lich/scripts/</code> directory.

=== create_symlinks.sh ===
Useful if you are doing development on OSX or Linux. Pass it an argument of the path to your <code>lich/scripts/</code> directory.

=== util/calculate_new_loot.rb ===
Compares <code>profiles/*-setup.yaml</code> files against <code>profiles/base.yaml</code> to determine proper loot_additions and loot_subtractions settings.

{{cat|Lich scripts}}

Lich script development

2019-07-11T01:43:41Z

HAZADO22: /* sorter */

{{RTOC}}

== Lich script libraries ==

These are lich scripts, but do not accomplish a task. Rather, they provide functionality that other scripts can take advantage of.

=== bootstrap ===
{{Lich script
|description=
|usage=You can turn on debug mode with <code>;e UserVars.bootstrap_debug = true</code>
|args=
|settings=
|uservars=
|children=
}}

=== common ===
{{Lich script
|description=A large set of helper functions for common actions shared by many scripts.
|usage=
Probably the single most useful function in this file is <code>bput</code> (short for 'blocking put').

bput is designed to be a more robust version of fput in situations where you know the desired response from the game. Unlike fput which will resend the same command repeatedly until it sees the desired message first from the game, bput only sends a given command one time (unless round time or type ahead errors occur) and then waits for the desired response. if the desired response isn't seen bput will eventually time out and echo debugging information.

This would never work because the game sends a response line "You search around..." before "Roundtime" is encountered:

<code>fput "forage grass", 'Roundtime'</code>

Similarly a command that can only succeed once can cause fput to hang. In this case, you have to deal with the failure case and just spam the command until failure in a noisy room with fput:

<code>fput "get box", 'you pick up', 'get what?'</code>

Lets you know with confidence if a box was picked up or if the item was missing:

<code>bput "get box", 'you pick up', 'get what?'</code>
|args=
|settings=
|uservars=
|children=
}}

=== common-arcana ===
{{Lich script
|description=A large set of helper functions for common actions related to spell casting, ability activation, etc.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-crafting ===
{{Lich script
|description=A large set of helper functions for common actions related to crafting.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-healing ===
{{Lich script
|description=A large set of helper functions for common actions related to health, wounds, and healing.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-items ===
{{Lich script
|description=A large set of helper functions for common actions related to manipulating items.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-money ===
{{Lich script
|description=A large set of helper functions for common actions related to money and coins.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-summoning ===
{{Lich script
|description=A large set of helper functions for common actions related to summoning weapons.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-travel ===
{{Lich script
|description=A large set of helper functions for common actions related to travel.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== dependency ===
{{Lich script
|description=
|usage=
For first time setup, see the Getting Started section of the repository README: https://github.com/rpherbig/dr-scripts/blob/master/README.md

You'll want to remove any of our scripts that you replace with this from the auto start so they aren't getting run twice.

Useful helpers:
* <code>get_script('name')</code> - fetch the script and start tracking it
* <code>get_yaml('filename')</code> - download the specified yaml file to your profiles directory
* <code>list_autostarts</code> - show all scripts that are started automatically
* <code>autostart(script)</code> - add a script to the autostart list
* <code>remove_autostart(script)</code> - remove a script from the autostart list
* <code>list_tracked_scripts</code>

You can turn on debug mode by passing 'debug' as an argument with <code>;dependency debug</code>
|args=
|settings=
|uservars=
|children=
}}

=== drinfomon ===
{{Lich script
|description=Updated info tracking for use in other scripts in DragonRealms
|usage=
* skill tracking - name/rank/xp
* info tracking - everything listed under info other than debt wealth and birthdate

Provides some additional commands to the user:
* <code>;banks</code> - Tracks your money and converts copper strings to plat format. Not all locations tracked.
* <code>;vault</code> - Tracks vault contents and location. -not all location included

Display experience gain in your Field Experience window:
* <code>;e UserVars.track_exp=true</code>
|args=
|settings=
|uservars=
|children=
}}

=== events ===
{{Lich script
|description=Flags are simple true/false string detectors.
|usage=
* <code><nowiki>Flags.add(<key>, <trigger>|[<trigger1,...,triggerN])</nowiki></code>
* <code><nowiki>Flags.add('test', 'exp help')</nowiki></code>
* <code><nowiki>Flags.add('another', ['exp help', 'a second message'])</nowiki></code>
This creates a new flag "test", which will return the matched string any time you see a message containing "exp help". Note that
the message will be treated as a regular expression and is case insensitive (google for more info) so be careful with
special characters, remember to use single quote strings if you're going to use special characters.
Calling add with the same key will overwrite any previous matchers and reset the flag.
Alternatively you can add an array with multiple matchers. If multiple messages match the flag will be set to the first match found.

* <code><nowiki>Flags.add('skillexp', '(\w[^:\(\)]+):\s+(\d+)\s\d+\.\d+%[^\(\)]*\((\d+)\/\d+\)')</nowiki></code>
This example will add a flag watching for the results of an exp message, specifically "exp skillname".
After sending "exp mech" to the game Flags['skillexp'] would contain...

["Mechanical Lore: 146 16.82% focused (20/34)", "Mechanical Lore", "146", "20"]

You can see the array containing entire matched string and the three capture groups containing
skill name, ranks, and mind state.

* <code><nowiki>Flags['test']</nowiki></code>
Returns the match if you've seen any message matching after you called add (or reset); false otherwise

* <code><nowiki>Flags['test'] = false</nowiki></code>
* <code><nowiki>Flags.reset('test')</nowiki></code>
Both of these commands have the same effect, reseting a flag as if it hasn't been seen yet.

* <code><nowiki>Flags.delete('test')</nowiki></code>
Removes a flag, stopping any tracking of it.
|args=
|settings=
|uservars=
|children=
}}

=== sorter ===
{{Lich script
|description=A script that converts inventories into sorted categories.
|usage=
|args=
|settings={{Lich setting|name=width|desc=<nowiki>(0-9999)</nowiki> Specify how many characters wide your game window is, and the script will display container contents in columns.}}^{{Lich setting|name=mute_old_inventory|desc=<nowiki>(True|False)</nowiki> Will mute the normal output for inventory, so you don't get sorted version and the normal output}}^{{Lich setting|name=sort_inv_command|desc=<nowiki>(True|False)</nowiki> Sorts the output from command "inventory"}}^{{Lich setting|name=sort_look_items_command|desc=<nowiki>(True|False)</nowiki> Sorts the output from command "look item"}}^{{Lich setting|name=ignore_categories|desc=Categories from base-items.yaml to ignore. Enter in regex format. Default is <code><nowiki>lootables|trash</nowiki></code>}}
|uservars=
|children=
}}

===spellmonitor===
{{Lich script
|description=
|usage=
* <code>DRSpells.prep_spell</code> - returns the string name of the currently preparing spell or nil
* <code>DRSpells.active_spells</code> - returns hash of spells keyed to duration e.g. <code>{"Bless"=>5, "Minor Physical Protection"=>12}</code>
** 0 means fading, removed from the hash is worn off
|args=
|settings=
|uservars=
|children=
}}

== Development tools ==

=== create_symlinks.bat ===
Useful if you are doing development on Windows. Set the LICH_SCRIPTS environment variable to the path to your <code>lich/scripts/</code> directory.

=== create_symlinks.sh ===
Useful if you are doing development on OSX or Linux. Pass it an argument of the path to your <code>lich/scripts/</code> directory.

=== util/calculate_new_loot.rb ===
Compares <code>profiles/*-setup.yaml</code> files against <code>profiles/base.yaml</code> to determine proper loot_additions and loot_subtractions settings.

{{cat|Lich scripts}}

Lich script development

2019-07-10T16:04:37Z

HAZADO22: Adding info for sorter.lic

{{RTOC}}

== Lich script libraries ==

These are lich scripts, but do not accomplish a task. Rather, they provide functionality that other scripts can take advantage of.

=== bootstrap ===
{{Lich script
|description=
|usage=You can turn on debug mode with <code>;e UserVars.bootstrap_debug = true</code>
|args=
|settings=
|uservars=
|children=
}}

=== common ===
{{Lich script
|description=A large set of helper functions for common actions shared by many scripts.
|usage=
Probably the single most useful function in this file is <code>bput</code> (short for 'blocking put').

bput is designed to be a more robust version of fput in situations where you know the desired response from the game. Unlike fput which will resend the same command repeatedly until it sees the desired message first from the game, bput only sends a given command one time (unless round time or type ahead errors occur) and then waits for the desired response. if the desired response isn't seen bput will eventually time out and echo debugging information.

This would never work because the game sends a response line "You search around..." before "Roundtime" is encountered:

<code>fput "forage grass", 'Roundtime'</code>

Similarly a command that can only succeed once can cause fput to hang. In this case, you have to deal with the failure case and just spam the command until failure in a noisy room with fput:

<code>fput "get box", 'you pick up', 'get what?'</code>

Lets you know with confidence if a box was picked up or if the item was missing:

<code>bput "get box", 'you pick up', 'get what?'</code>
|args=
|settings=
|uservars=
|children=
}}

=== common-arcana ===
{{Lich script
|description=A large set of helper functions for common actions related to spell casting, ability activation, etc.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-crafting ===
{{Lich script
|description=A large set of helper functions for common actions related to crafting.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-healing ===
{{Lich script
|description=A large set of helper functions for common actions related to health, wounds, and healing.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-items ===
{{Lich script
|description=A large set of helper functions for common actions related to manipulating items.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-money ===
{{Lich script
|description=A large set of helper functions for common actions related to money and coins.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-summoning ===
{{Lich script
|description=A large set of helper functions for common actions related to summoning weapons.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== common-travel ===
{{Lich script
|description=A large set of helper functions for common actions related to travel.
|usage=
|args=
|settings=
|uservars=
|children=
}}

=== dependency ===
{{Lich script
|description=
|usage=
For first time setup, see the Getting Started section of the repository README: https://github.com/rpherbig/dr-scripts/blob/master/README.md

You'll want to remove any of our scripts that you replace with this from the auto start so they aren't getting run twice.

Useful helpers:
* <code>get_script('name')</code> - fetch the script and start tracking it
* <code>get_yaml('filename')</code> - download the specified yaml file to your profiles directory
* <code>list_autostarts</code> - show all scripts that are started automatically
* <code>autostart(script)</code> - add a script to the autostart list
* <code>remove_autostart(script)</code> - remove a script from the autostart list
* <code>list_tracked_scripts</code>

You can turn on debug mode by passing 'debug' as an argument with <code>;dependency debug</code>
|args=
|settings=
|uservars=
|children=
}}

=== drinfomon ===
{{Lich script
|description=Updated info tracking for use in other scripts in DragonRealms
|usage=
* skill tracking - name/rank/xp
* info tracking - everything listed under info other than debt wealth and birthdate

Provides some additional commands to the user:
* <code>;banks</code> - Tracks your money and converts copper strings to plat format. Not all locations tracked.
* <code>;vault</code> - Tracks vault contents and location. -not all location included

Display experience gain in your Field Experience window:
* <code>;e UserVars.track_exp=true</code>
|args=
|settings=
|uservars=
|children=
}}

=== events ===
{{Lich script
|description=Flags are simple true/false string detectors.
|usage=
* <code><nowiki>Flags.add(<key>, <trigger>|[<trigger1,...,triggerN])</nowiki></code>
* <code><nowiki>Flags.add('test', 'exp help')</nowiki></code>
* <code><nowiki>Flags.add('another', ['exp help', 'a second message'])</nowiki></code>
This creates a new flag "test", which will return the matched string any time you see a message containing "exp help". Note that
the message will be treated as a regular expression and is case insensitive (google for more info) so be careful with
special characters, remember to use single quote strings if you're going to use special characters.
Calling add with the same key will overwrite any previous matchers and reset the flag.
Alternatively you can add an array with multiple matchers. If multiple messages match the flag will be set to the first match found.

* <code><nowiki>Flags.add('skillexp', '(\w[^:\(\)]+):\s+(\d+)\s\d+\.\d+%[^\(\)]*\((\d+)\/\d+\)')</nowiki></code>
This example will add a flag watching for the results of an exp message, specifically "exp skillname".
After sending "exp mech" to the game Flags['skillexp'] would contain...

["Mechanical Lore: 146 16.82% focused (20/34)", "Mechanical Lore", "146", "20"]

You can see the array containing entire matched string and the three capture groups containing
skill name, ranks, and mind state.

* <code><nowiki>Flags['test']</nowiki></code>
Returns the match if you've seen any message matching after you called add (or reset); false otherwise

* <code><nowiki>Flags['test'] = false</nowiki></code>
* <code><nowiki>Flags.reset('test')</nowiki></code>
Both of these commands have the same effect, reseting a flag as if it hasn't been seen yet.

* <code><nowiki>Flags.delete('test')</nowiki></code>
Removes a flag, stopping any tracking of it.
|args=
|settings=
|uservars=
|children=
}}

=== sorter ===
{{Lich script
|description=A script that converts inventories into sorted categories.
|usage=
|args=
|settings={{Lich setting|name=width|desc=Specify how many characters wide your game window is, and the script will display container contents in columns.}}^{{Lich setting|name=ignore|desc=Categories from base-items.yaml to ignore. Enter in regex format. Default is <nowiki>lootables|trash</nowiki>}}
|uservars=
|children=
}}

===spellmonitor===
{{Lich script
|description=
|usage=
* <code>DRSpells.prep_spell</code> - returns the string name of the currently preparing spell or nil
* <code>DRSpells.active_spells</code> - returns hash of spells keyed to duration e.g. <code>{"Bless"=>5, "Minor Physical Protection"=>12}</code>
** 0 means fading, removed from the hash is worn off
|args=
|settings=
|uservars=
|children=
}}

== Development tools ==

=== create_symlinks.bat ===
Useful if you are doing development on Windows. Set the LICH_SCRIPTS environment variable to the path to your <code>lich/scripts/</code> directory.

=== create_symlinks.sh ===
Useful if you are doing development on OSX or Linux. Pass it an argument of the path to your <code>lich/scripts/</code> directory.

=== util/calculate_new_loot.rb ===
Compares <code>profiles/*-setup.yaml</code> files against <code>profiles/base.yaml</code> to determine proper loot_additions and loot_subtractions settings.

{{cat|Lich scripts}}

Zombie goblin

2015-11-05T15:53:19Z

HAZADO22: You can't skill these anymore

{{Critter
|Critter Name=Zombie [[race is::Goblin]]
|MinCap=5
|MaxCap=32
|BodyType=Biped
|new=No
|Skinnable=no
|Has Coins=yes
|Has Gems=yes
|Has Boxes=yes
|Evil=undead
|Construct=no
|Corporeal=yes
|BackStabbable=yes
|Casts Spells=no
|Stealthy=no
|Special=no
|Attack Range=Melee
|Province=Therengia, Zoluren
|City=Riverhaven, Tiger Clan
|MapList=*{{rmap|31f|Northeast Wilds (31f)}}
|MapList2=*{{rmap|4 | Woodland Path (4)}}
|hasskin=Yes
|Skin Name=
|Skin Weight=
|haspart=Yes
|Part Name=
|Part Weight=
|hasbone=Yes
|Bone Name=
|Bone Weight=
|RequiredRanks=
|MaxVal=
|MaxArrangedVal=
|Manipulated=no
|mskill1=
|mskill2=
|mcap=
}}
__NOTOC__

==Description==
The zombie goblin at first appears to just be a normal goblin, but flesh is peeling off of its body and its equipment is missing or in dire need of repair. Unfortunately, this just makes it smell even worse than a normal goblin. Its eyes glow a dim red with some sort of weak unholy power, and its limbs twitch in jerky movement due to its rigor mortis. It seems to be scanning the area looking for live meat to consume.

==In Depth==
If they defeat another monster, they eat their brain: 
The zombie goblin crouches next to a brown burrower's body and rips into its head to devour the brains within. 
North of Riverhaven they tend to swarm. 
Significantly easier than Crossing goblins.

===Equipment/Loot===
*It is wearing a {{cloot|a|rotting leather coat}}.
*It is carrying a {{cloot|w|rusty scimitar}}.
The coat and scimitar will crumble into a fine ash if a player interacts with them.