Version 2.965

Bug preventing Towny opt-in from properly taking hold, fixed.

Work done on dispatcher to make it capable of creating new routes and PO's as well as
deleting them, hot.  Postal restart is no longer required for these types of changes.

Dynmap support, like the dispatcher, no longer needs to restart Postal to update
addresses or PO markers.  Changes affecting Dynmap now take place as they occur.
Labels for post offices and addresses have a different format when in a Towny
town.

Other improvements: /setroute no longer needs parameters. It will automatically select
the address the player is closest to. The route editor now clears the quickbar so that you
have nothing clunky in your hands while designing routes. It places a compass in the middle
slot, which points to the address the player is designing the route for. Exiting the route
editor restores the quickbar the way it was.

More geographic awareness implemented to the info listing commands.  For example, /plist,
without parameters, in addition to listing online players, now shows the distance and the
compass heading to each player, as well as the closest Postal address or post office
each player is near. The compass is always lined up with Minecraft coordinates to make the
compass useful.  [F3] is an alternative.  Players listed this way only include the
ones in the same world.


Version 2.96

Postal log kept out of general player hands to prevent using copies as a trade commodity.

Breaking a target mailbox after the postman left the postoffice was causing a non-serious
stack trace.  Now handled.

Aliases set up for the often used commands, documented on the help screens found by typing
/postal without parameters. Also documented in plugin.yml, the source.

Item shipping with the /package command now includes extended definitions of items that
carry details of the item type in the damage integer.  Items like potion, that would be
recieved as a water bottle, and colored wool that came as white wool.  The written
book is a free standing data container holding everything required to re-create the
stocked chest it defines.

General tightening up of '/postal restart' to reinitialize all arrays and make sure
outlaw goals for deleted npcs are cleared.  These un-cleared goals were causing non-
fatal, but messy stack traces that were hard to decipher.  The cooling time for restart
was extended to 10 seconds, from 5 seconds.

Dynamic waypoint adjustment now uses an expanded lookup table of blocks treated like air.
ie:  tall grass is not air, but it should be treated like air for the purpose of finding
the actual waypoint block fed to the npc navigator.  There are currently 34 of these
types of blocks, up from around 10.

Geographical awareness implemented in commands like /tlist and /alist as well as the helper
system designed to help a player locate and complete a desired address.  For example, if
/alist is entered without a parameter, the closest town will be selected and it's addresses
listed instead of being shown a help screen.  /tlist with no arguments displays the town list
alphabetically as usual, but now includes the towns or post offices in the same world at
the bottom of the list, by distance, so the player may be aware of what he/she is close to.
The block distance and compass direction to the town are included.

Compass direction info now included in address and post office lists complementing the
general, geographic info displayed.  The compass directions are given in the standard
Minecraft, compass directions [F3], and the compass automatically aligns itself to this
coordinate system so that it may be used.

A new command:  '/gps <PostOffice> [Address]' and perm node 'postal.gps'.  This command sets
the player's compass to either a post office location, or a two part address.



Version 2.95

Route and post office closing system implemented a few versions ago refined and expanded.  POs
or routes opened or closed with the /openxxx and /closexxx commands now stay that way through
a server restart.  This status is now in the database.

Upon startup, Postal now checks the defined post offices, addresses and central and determines if
it has the bare minimum to start. If so, and configured to automatically start, it will proceed.
Postal no longer refuses to start if it finds problems like an address without a route.  It
simply closes the route with a message and continues.

Address listing with /tlist as well as the command infrastructure is now Towny aware and
responds to different contexts.  Post offices in Towny towns are now considered children of
that town.  Post offices outside of Towny behave as they always have.  What the player sees in
messages changes depending on whether he/she is located in a Towny town.  Console output
reflects the Towny opt_in setting.  Opted in clearly shows Postal post offices as children of
a particular towny town, or Postal.  The two part address remains the same and can be thought
of as [PostOffice] and [address] pairs instead of the former [town] and [address].  Post
offices in a Towny town will naturally be named something reflecting a part of the town.
Outside of Towny, post office names will probably sound more like cities.  It makes no
difference to Postal.  Postal concerns itself mostly with making the address, any address,
easy to find, and getting mail and shipments there.

New config setting, 'Setings.Wpnt_hilite_id' contains a block id type, an integer below 256,
decimal.  This is the block type the waypont editor uses to highlight existing waypoints, and
waypoints in progress.  Thw waypoint editor now uses a lookup table containing valid block
surfaces for waypoint marking.  Nothing else is permitted.  The highlighting method has changed.
Postal formally marked waypoints with redstone dust.  This became problematic in certain
situations where the surface would not tolerated it, or an adjacent block lke a chest with a
sign on it would not permit it since the sign is actually occupying the block above the desired
waypoint block.

Postal now tightly controls the block type that may be used to mark waypoints.  Highlighting
may be safely done by temporarily replacing the marked block with something visible.  The
default is redstone block.  There are no competing entities when the highlight is the surface
block itself.  The material type as well as the extended data are saved so that the original
blocks are restored the way they were upon highlite removal.

This cut of Postal marks a deep integration with Towny.  On Towny turf, Postal follows everything
appropriate, as defined in Towny.  There is nothing to do in Postal for Towny integration other
than to opt in the 'config.yml' file. Postal updates itself as mayors and homeowners come and go.
Even the names displayed on mailboxes and post office chests are kept current.

Towny owners and town staff automatically have the same privileges of ownership Postal owners
have.  Growth control based on a percentage of town blocks prevents misuse or abuse of
Postal resources.  Configurable in the configuration file.


Version 2.941

Location used to determine the owner of a Towny plot changed from the last waypoint on a route
to the location of the mailbox chest.

Refinements to the Towny plugin detection to hopefully eliminate false positives on the status
of the plugin.

Towny support expanded to automatically assign post office, ownership privileges to the mayor
of the town the post office is located in.  Like Towny owned plot integration, 'settings.towny'
in 'config.yml' must be set to 'true' for this to be in effect.

Assistants to the mayor with the rank of 'postal' have admin privileges for the post office(s)
in their town.

Postal automatically verifies and permits mayor, or ranked assistants to use the /setlocal
command in their town to create one or mor post offices.

Defining new addresses with the '/setaddr' limitted to the mayor, or ranked assistants.

Towny plot owner may define their own, new route to the post office, but  must be standing on
own plot when invoking '/setroute' for the first time. This is not necessary for editing
existing routes.

Subsequent changes in town mayor or plot owners are automatically registered by Postal.  The
absence of a mayor or plot owner results in 'Server' ownership.  Ownership is verified and
updated each visit to an address by postmen, and each visit to the post office by the
postmaster.


Version 2.94
New soft depends on Towny and WorldGuard.

If WorldGuard or Towny are installed, item shipments may only be accepted in regions that the
player has build permissions.  This may be overridden with the node 'postal.accept.bypass'

Acceptable mailbox chests now include trapped chests.

New setting in 'config.yml', 'settings.towny'.  It defaults to 'false'.  When set to true any
mailbox determined to be on a Towny plot will have the plot owner's name put on the mailbox.
Towny plot owners will automatically enjoy the normal Postal ownership privileges.
Unowned Towny plots will revert to 'Server' as the name on the mailbox.  This applies only to
Towny plots, and will override the Postal /owneraddr setting.  Leaving 'settings.towny' at
'false' maintains the current behaviour.


Version 2.93

On server startup, postmen and postmaster cooling settings set to 10 seconds.  When all of the
postmen have been initialized, the settings in 'config.yml' are applied.

Mailed letter listener modified to not only prioritize the route it is on, but to also take the
postman off his break defined by 'settings.postman_cool_sec'.  As the number of post offices or
towns continue to increase, admins may choose to define longer cooling periods for the postman
to spend in the post office.  This change will make the length of the postman's break irrelevant
to the overall speed of the mail delivery because the postman will interrupt his break to
pickup a letter that was mailed.

Postmaster preemptive mail handler modified to cut his break short for the same reason above.

Postal looks for the Citizens api class on startup and aborts with a message if not found
instead emitting a stack trace.  Of course, if the reason Postal can't find the Citizens class
is because it is not installed, CraftBukkit will make a fuss about running a plugin without
a declared dependency.  :-)

Tweaked door navigation to synchronize with Citizens2 build 760 path'ing refinements.

Stopped making duplicate copy of the shipping label and inserting into the shipping container
when /package'ing.  It is not necessary anymore since the shipping label, when /accept'ed is
stamped as received and placed directly in the player's hand.  /refuse still removes original
statement from player's hand, stamps it refused, and puts it in the shipment returned to sender.

Replaced deprecated Bukkit, door class with direct, bit manipulations to the state of door blocks.

Version 2.92

Clicking on a postal log formally drops any item the player may have in hand before putting
the postal log in the player's hand.  This prevents loss of player inventory.  The same
safety precaution has been applied to shipping labels before they are placed in the player's
hand.

New config.yml setting 'lookclose_on_route'.  'true' is the default.  'true' makes the postman
aware of other players while walking his route.  He will look at the player and appear a little
distracted by other players, but stays on route.  Seems more human and less programmed.  'false'
causes the postman to be more focused, and generally does not acknowledge the existence of players
aside from mouse clicks.  In the postoffice, waiting for the next route lookclose is turned on
regardless of this setting.

Fixed bug with /package command excluding items when itemized on the shipping label.  Pages on the
written book were exceeding their character capacity and being truncated when many items with
long names were on the same page.  Item names were also being unnecessarily padded with trailing spaces.

Double chests are now formally rejected as shipping containers.

Stamped statement now replaces the un-accepted statement in player's hand on /accept instead of
going into the accepted chest.  This facilitates the sending of completely full chests and is
probably more intuitive to the player.

/accepted chest no longer identified with a sign when accepted.  It is not necessary.  It was also, upon
opening, being incorrectly labeled as a Postal mailbox.

The general system watchdog was not allowing for extended cooling intervals set for postmen with the
settings.postman_cool_sec setting in config.yml.  This was fixed by using the value in this setting
to make sure the system setting is long enough to allow for anything set here.  The individual postmen and
postmaster watchdogs are not affected since they have flags indicating cooling periods, periods ignored
by the watchdog.

Version 2.9

New softdepend dynmap.

New, full dynmap implementation.  May be optionally disabled, but automatically disabled
if the dynmap plugin is not installed.  Map features separate Postal layer.  Labels for
post offices and addresses are plotted.  Locations for both postmen and postmaster
are updated in realtime.  Routes are plotted as they are in use, and removed when
inactive to reduce clutter.  NPC plotting is based on actual position, therefore showing
route deviation, if present.  All map entities may be clicked to obtain detailed information
and realtime statistics.

New config.yml setting Dynmap.  Set to 'false' to disable all Dynmap hooks in Postal.  Will
Prevent Postal from automatically using Dynmap when Dynmap is installed.

Restart sequencing reorganized and hopefully, strengthened up to the point of not needing to be
revisited again.





Version 2.8

New command /distr <all/owners> [town] [expiration_days]
This is an op or admin tool.  It facilitates the instant distribution of a written
book in the player's hand to Postal addresses.  Distribution may be to all addresses,
or just owned addresses.  The distribution may be further filtered by a town name.
Distributions include a cover page indicating general information including the
original title and author of the written book.  The title, as delivered will be
[Distribution] and the author field will contain a number ie: '1234567890' that may
be used to uniquely identify the document.  This number also represents the expiration,
in Unix time, of the document.  This command does not require the Postal dispatcher
to be running.  Distributions trigger new mail indicators for both player login and
mailboxes.

New permission node 'postal.distr'

New setting in 'config,yml'. 'distr_exp_days'  Takes a number from 1 to 30 to set
the default expiration of distributions.  Default value is 7.

Full mail boxes allow mail to take precedence over distributions.  If the postman
encounters a full mailbox, he will look for distributions to delete.  He will make
room, deleting oldest distributions first.

Distributions get an expiration date when distributed.  This may be 1 to 30 days,
real time.  The postman checks for expiration each visit, and deletes expired
distributions.  Unattended mailboxes are therefore managed and kept clean.

Postal NPC's are now managed by the names configured in config.yml instead of strict
id numbers received at creation.  This makes it possible to automatically clean up
shadow postmen left over from a bad server shutdown.  This also improves compatability
with other Citizens characters and eliminates any special steps with Postal in regards
to preserving or saving the other NPC's.  Color format characters are part of an
NPC name and further help distinguish Postal names from other NPC names.

Bug: opening mailbox by clicking on the chest instead of the sign failing to
clear new mail indicator.  Fixed.

Version 2.79

Default heartbeat changed back to Synchronous, Asynchronous may be configured in
config.yml

New option in config.yml to turn automatic heartbeat calibration on/off.

NPC creation and spawn allowed to retry on exception instead of completely
restarting Postal.



Version 2.78

Issue where shipment mailed at a post office not properly received into system, fixed.

Dispatcher heartbeat put on a Asynchronous thread.

New config.yml setting: 'prevent_all_npc_despawn' prevents non-Postal NPC's from
despawning.  These are Citizen2, player type NPC's.

General code clean up and optimization.



Version 2.77

/package now incorporates text from a written book held in the players hand into the
statement generated.  If there is nothing in the players hand, Postal will look for
a written book titled 'statement' to use.

Chest selection for shipping now deliberately excludes Postal mail boxes.  This was an issue
for players that locate their shipping containers next to a mail box.  This sometimes resulted
in Postal choosing the mail box instead of the shipping container with the /package
command.  Currently there are no constraints for the shipping container location verses
where the shipping label is mailed.  The thought is that some players may prefer to pack
their boxes in their residences and mail the shipping labels elsewhere, perhaps in the
mailbox outside the house.  Big shippers may prefer to prepare many shipments at once then
mail all the shipping labels at once.  The packages remain out of sight until received by
Postal.

Shipments are now protected.  Until received by Postal, shipments are sealed, and may only
be destroyed by a player with the original shipping label in hand (or an admin).
Shipments remain protected while in the Postal system, and while waiting to be accepted
at the recipient's mailbox.  Normal ownership privileges apply concerning final access
access at the destination.  Once /accepted, the shipment may be placed wherever desired
and is no longer protected.  /refused shipments are returned to where it was packed
and remains sealed to all but the sender or admin.



Version 2.76

Formally set (and validate) maximum name lengths of post_office, town and player to
15 to match the maximum line length of a sign.  Formerly, and a bit informal and not validated,
the name length has been declared 14 characters.  A player name may actually be 16
characters, as permitted by Minecraft.  All of the Postal routines and data storage have
been updated to allow for this slightly longer possibility.  Postal simply drops the
last character of a player name if it is 16 characters and assumes that there will
not be any more than one unique completion of similar 16 character names missing the last
character.

Postal log now occupies slot 0 of a Postal chest.  This new assumption allows Postal to
readily find the log without iterating through the entire chest.  The postal log format has
changed, and the saving of full logs to postal archives has stopped.  The new postal log
format is one page only instead of 50 pages.  The time stamp order has changed from the
last stamp going at the end of the book to it being the first.  The set of stamps shown
on the first page are ordered newest to oldest.

The new postal log location, the new, one page format along with the recent sign
id of Postal chests provides a more efficient infrastructure, a hybrid of the sign/book/chest
data object and the hierarchical data structure in a yaml format.  Much code optimization
using this new infrastructure has taken place.

Postal, once per startup, cleans out Postal chests of anything that is not a written
book.  Obsolete files such as old postal logs and postal archives are also removed.

New mail notification to address owners has been expanded to include a message when
the player joins.  All owned addresses are scanned for unread mail, and reported.
New mail notification on Postal chests has been changed from a redstone torch in
front of the mailbox, to highlighting the first line on the Postal sign with red.

Version 2.6

CB_1_4_6 version conforms to Bukkit non-version model, therefore rendering it
non-version-specific for Bukkit CB_145_R1 (Recommended Build) and beyond.
Users running Bukkit prior Bukkit builds need to use the CB_1_4_5_R02 builds
of Postal.

New advanced mailbox detection and labeling system.  Once a mailbox is identified
by Postal a detailed sign is posted on the front of the mailbox.  Postal always
looks for a signed chest first.  If the sign details match the chest is used.  If
the signed mailbox is not found, Postal falls back on proximity and/or postal log
confirmation.  This is a far more efficient method of mailbox detection, and serves
to clearly identify mailboxes to the player as well.

Shipments are sign identified as such, making their overall roll in the Postal
system clearer.

Preemptive mail handling has been expanded to include the PostMaster, or Central
postal system servicing local post offices.  This replaces the former round-robin,
central scheduler and is designed to keep mail moving along efficiently as the
number of post offices continue to increase.

Version 2.5

Global searching. /tlist and /plist have been expanded to facilitate global searching
by address name or player name.  All three of these commands are fully functional in
game, or on the console.

/tlist will now take a search parameter.  This command will still
behave as it always has and alphabetically list the town names without a parameter.  The
quantity of towns is assumed to always be of a length not requiring any more than an
alphabetized list for quick reference.  If given a parameter /tlist will now, recursively,
search each town on the server for addresses matching the search parameter and list them.
'/tlist *' will list, alphabetically, every address on the server.

/alist is not effected.  It will still attempt to complete a town name and list all the
addresses in the town, or display town names close to the search parameter.

/plist will still quickly list players names that have been on the server matching
the search parameter.  However, if the search parameter is enough to uniquely
complete a player name, Postal will globally search all of the postal towns and
addresses for player ownership.  Any Post office or town owned by the matching player
name will be listed.

Player teleporter problem fixed.  Player sometimes arrived before the world blocks
did and allowed the player to fall until the blocks showed up.  This may be caused by
the target being in an unloaded chunk, or a simple timing issue between player and
block appearance.  The solution seems to be to call for chunk load while delaying player
slightly.  An additional reality check by Postal verifies actual player position after
teleport, and follow up with habitability check and final reposition if needed.

Uniform components have been moved to 'config.yml' for both the postmaster and local
postman.  Item id's are required and will be checked for validity.  Invalid id's
will default to nothing.

New statistics holders for the post office portion of the dispatcher, called the queue.
cem_time is stamped each time the post office is visited by the postmaster. cen_count
keeps a running count of visits.  cen_interval holds the time in seconds between
visits.

Item shipping implemented with the addition of three, new player commands.  /package,
/accept and /refuse.  /package <town> <address> [player] creates a shipping label for
the chest the player is standing next to.  The shipping label contains a complete list
of the items and quantities in the chest.  A copy is placed in the player's hand, and
another copy is placed in the chest.  This shipping label may be treated like any other
addressed, mailable book.  It may be re-addressed with /addr or /att.  To ship the chest
the shipping label is simply placed in a designated mailbox.  When it is picked up by
the postman, the chest will vanish and be in the postal system.

On delivery, the recipient may /accept the shipment or /refuse it.  To accept, the
recipient, with the shipping label in hand, walks to where the chest should be placed
and enters the /accept command.  The shipment will appear directly in front of the player.
Chests will automatically stack if there is already one there.

To refuse a shipment the player simply enters /refuse with the shipping label in hand.
The shipment will be immediately returned to the sender.  It will appear exactly
where the sender packed it, or stacked if there is another chest has been placed there
since it was shipped.

A personal message may be included in the compiled shipping label by including a written
book titled 'statement' in the chest to be shipped. The text in this book will be included
after the line item details of the chest contents. This book will also be replaced by the
formal shipping label.


Version 2.1

Improvements to hot route editing using the new route closing capability.

Four new commands, console and player to control the open/close status of post office and
routes.  /openlocal, /openaddr, /closelocal, /closeaddr.  Changes made by these commands
remain effective until Postal is restarted.  Even though a local post office is closed
the Postmaster is still servicing it.  Books may still be mailed at the post office and
they will be processed normally.  Mail may also be picked up at the closed post office.
It just won't be delivered to residences, nor will mail be picked up at residences.  These
new commands require administrative privileges or ownership rights to use.

New scheduling control.  Post offices may be opened and closed, hot.  Individual routes may
be similarly controlled.  Provides increased resolution for in-game, console or outside control.  This
allows all routes to be individually controlled.  This will have a place in the
coming economy implementation as well as provide a way for other apps to influence
the Postal dispatching.  There is a new set of commands detailed above.

new 'config.yml' settings 'Join_message' and 'Residence_cool_ticks'.  'Join_message' is the message
the players see when joining.  Accepts standard color codes, and variable %player% expands to the
name of the player joining.  May be set to ' ' to skip message entirely.  'Residence_cool_ticks' is
the amount of time, in ticks the postman pauses at each residence on his round.

Menu displayed when entering 'postal' reorganized to provide a more relevant list of
commands based on the players permissions or ownership.  There are now three distinct menus;
player, owner and admin.  Players get a menu designed for them.  Any player that owns a route
or post office will get the owner's menu.  Admins get the full list.

Added '/first', '/mid' and '/last' commands to waypoint editor.  Use to quickly position
player along a route.

Bug in 'postal cstalk' fixed.  The wrong spawn location was being reported.  The actual,
recorded location was correct, however.

Three new settings in 'config.yml':  'Postman_cool_sec', 'Central_cool_sec', 'Heart_beat_ticks'.
'Postman_cool_sec' is used to configure the amount of time, in seconds, the postman stays in the
post office in between routes.  'Central_cool_sec' is the amount of time the postmaster stays at
each post office during his rounds.

'Heart_beat_ticks' is the Postal heart beat interval.  Anything entered by the user in this field will be
used as a starting point for Postal.  Postal calibrates itself and saves the calculated result there.

Dispatcher layout in 'config.yml' has been reorganized and slightly refactored.  Interval field has
been added for future use.

Static chunks are no longer stored in 'config.yml'  They are now held in a memory array.

Postal now scans all residential mailboxes for outgoing mail when it starts up,or is restarted.
Postal also listens for new mail and expedites the route with new mail.  However, when the Postal
is restarted it rebuilds the dispatcher from scratch and starts all routes from the top.  Expedited
routes containing mail were lost during the rebuild resulting in the temporary loss of the preemptive
mail-handling of the system.  Scanning residential mailboxes as it re-builds the dispatcher restores
waiting mail to the top of the queue.

Three more 'config.yml' strings:  Chat_onroute, Chat_postoffice and Chat_collision.  What the
NPC says during the implied contact.  Variable %player% in the string will be expanded to the
player name making contact.  These strings accept the standard '$' color codes.

/alist command now displays the time it takes for the postman to walk each route.

Added two more 'config.yml' switches; 'allow_monster_spawn' and 'chunk_overlap'.  The first switch,
when set to 'false' (default), will prevent monsters from spawning along postal routes, post offices and
residences serviced by the post office.  This is, technically, the chunks monitored by the Postal
chunk manager.  The chunk overlap switch makes it possible to expand the managed area if desired.
The default is 0, the minimum required by the postal system to function.  The maximum is 10.
New console command 'postal chunks' displays the size of the chunk pool.  It complements the
chunk overlap switch as a way to view the effect of different values.


Version 1.9

Recent feature added to dependency Citizens2 had the NPC's despawn when near any chunks that were unloaded.
This typically happens when live players leave an area.  The Postal watchdog was compensating for this by
nudging the NPC's back to existence.  Now, if a postal worker is targeted by such a despawn instruction, the
event is canceled.  There are no more route interruptions caused by the simple absence of live witnesses.

Route editor.  This editor has been modified to be more like the Citizens2 path editor by implementing both mouse
buttons.  Left click marks a waypoint, right click undoes the last waypoint.  Further, double clicking on the final
waypoint block exits the editor.  The editor will not mark the same block more than once in a row.  Click the
same block as many times as you want, it will only record once.  Double click it and you exit the editor with that
last block as the end of the route.  Typing difficult commands in the waypoint editor is no longer necessary.
A new command processor dedicated to the person in the route editor is in place.  Even though the new mouse navigation
eliminates the need to type any commands while editing, they are still available, and no longer require the
preface:  '/setroute'.  Instead of '/setroute exit', it is now just '/exit'.  The same is true for /new and /undo.
The route editor will not allow any other interaction other than route editing while in the editor, nor will
it let you forget that you are in the editor.  It will also exit automatically if the user quits while in an editing
session.

Redstone dust is now used to highlight waypoints while in the route editor.  When editing an existing route, existing
waypoints are highlited, and the player is teleported to the last waypoint.  Right clicking near the end waypoint
removes it without moving the player, /undo removes it and advances the player to the new, route end.  Right click
as you are laying forward waypoints and you will get a distance reading relative to the last waypoint behind you.
Double (left) clicking the final waypoint exits the editor and removes the waypoint highlighting.

Listeners have been reorganized and consolidated.  The only listeners normally left on are for inventory (mail)
control and management, and player interaction - item and chest security.  Listeners used for route editing are
only on when in use.  They are turned off when exiting the route editor.

Sign identification of mailbox chests.  Was changed from a simple [mail] label to a more specific [address_name]
label on version 1.8  The id algorithm was relaxed slightly to accommodate names longer than a sign line will
permit.  The text between the brackets may be less than the full length of the name, as long as it matches, case
insensitive.  The two brackets are mandatory.  It is not unusual for there to be other copies of the address
name nearby.  The brackets serve to distinguish it as a mailbox designator.

Both ends of a route have definitions that can seem slightly ambiguous or confusing.  Routes start at the local
post office with waypoint 0, the postman's first step.  The route ends in front of the mailbox at the residence.
This has the highest waypoint number.  While there are the two route endpoints indicating where the local post
office is, as well as the residence location, there are also separate, and independent designations that are very
similar; /setlocal, and /setaddr.

This ambiguity on the residence end has already been addressed by automatically synchronizing the /setaddr location
with the final waypoint set using /setroute.  /setaddr may not be invoked after a route is defined, therefore
eliminating any possible re-set errors later on.  /setaddr has as it's main purpose, the careful and deliberate
naming of a new address and approximate location, and is the admin's tool.  /setroute is the primary tool used
by a owner/resident, and remains flexible, allowing the resident to be blissfully unaware of any of these
location distinctions.  Nor anyone else, for that matter (except the developer).

Back to the post office end of a route.  It was still possible to screw up the route system by re-setting the
local post office location erroneously after a set of routes for it is in place.  The fix was easy
enough - just reset it correctly.  The post office end is more complicated than the residence end because it is
common to all of the routes.  You can't move the post office without redoing all of the routes it services.
So, this has been tightened up to protect us from ourselves.  /setlocal may still be used to reset the
formal location for the local post office, but the user is not allowed to screw things up anymore.  The location
defined by /setlocal is the spot where postman stands in between routes.  It should be near waypoint 0 for each
and every route connected to the post office.  /setlocal now verifies that the new position is close enough to
each route start, or it won't allow the change.  It will tell you why, however.  It might be just one errant route
causing a problem.  It is also a diagnostic tool.

New command /showroute, both player and console.  Usage is '/showroute <town> <address>'  Use it to highlight
waypoints on a route with redstone dust.  The waypoints remain highlighted for a minute or so, and them are
cleared.

New console monitor toggle cstalk.  Useage: 'postal cstalk'.  Use to monitor the regular chest seeking
activity by the npc's  Shows what was found, selected and why.

Fixed bug with the schedule promoter.  When using /setroute to create a new route it
will automatically push the schedule of that route forward so the edited changes may
be immediately observed.  /setroute is also used to create new routes.  New routes are not
live until the next Postal restart.  The schedule promoter was not checking to see if
the route was active before trying to promote it, causing a fault.

New command confirm mechanism affecting most of the commands, player and console.
When invoking a command, the user is now presented with a message indicating specifically
what it is going to do.  And, the user is asked to enter a '/' to confirm.  Postal
does extensive command completion in an endeavor to minimize user typing.  Just a few
letters of a name may expand to a complete, 16 character name if Postal can determine
uniqueness.  This confirm mechanism makes it possible to take full advantage of Postal
name completing.


Version 1.8

Fixed bug caused by undo'ing past waypoint 0 using /setroute.  Attempting to undo past the
first waypoint now automatically invokes the equivalent of '/setroute new'

Fixed minor bug when placing a redstone torch, new-mail indicator in front of a chest that already had one.
Caused subsequent placements to unattended chest to litter area with unplaced torches.

Require Postal to be stopped before allowing post office or address deletion.  No longer uses
name completion for town or address names when deleting.  Requires names to be typed out, completely
and accurately, although not case sensitive.

Change 'postal expedite' command to straight 'expedite', both player and console.

New command 'plist <string match>'  It lists player names matching a search string, case insensitive.
It compliments existing commands /tlist and /alist to help players address and direct mail efficiently.
Postal commands such as /addr, /att, /owneraddr and /ownerlocal that may use live player names, use
the same name completion methods for the player parameter.

Existing commands, not implemented /owneraddr and /ownerlocal are now implemented.  These are used to
establish, or define player ownership of specific addresses or local post offices. These commands also
remove ownership designation when 'none' is used as the player parameter. They also provide a
general association of a specific player to specific address(es).  For example, mail sent to an address
to the attention of 'current resident' may still be associated with a player if the address belongs to
a player.  The player can be informed of the delivery, and there are economy options that will eventually
come into play.  Post offices can be private, or public enterprises.

 /tlist and /alist expanded to include owner info along side town and address names.

Mail delivery status looks for address ownership if addressed mail is not sent to a specific
player's attention (/att).  Address owners are advised of 'current resident' mail delivered to
their address.

Mail delivery format changed to indicate sender and recipient as author and title.  Original character
case retained.  May be seen when mouse'd over in mailbox, without selecting or opening book.  Mail
formerly showed the original, signed-book title and author when NPC delivered.

A Postal Log is now maintained in the post office chests as well as residence chests.  This aids in the
identification of all official, Postal chests and reduces overall complexity.

Chest protection.  Mailbox chests, identifiable as a chest with a postal log, may only be removed or
destroyed by an op, player with 'postal.admin' permission, owner of the post office it is serviced by,
or owner of the address it belongs to.

Chest access.  Anyone may look in a mailbox chest and observe written books. The sender and recipient
is plainly visible when mouse'd over, but nothing else.

The '/postal admin' command turns off Postal security listeners.  It has been changed from
a toggle on/off switch to a timer.  When invoked, it quietly turns the security off for 60 seconds.  This
affects all users on the server.

Mail access:
    When sent to the attention of a player, any address:
        May only be accessed by that player, the sender, address owner, 'postal.inspector', or op/postal.admin.
    When sent to 'current resident' and the address is owned:
        May only be accessed by the address owner, the sender, 'postal.inspector', or op/postal.admin.
    When sent to 'current resident' and the address is not owned, or a Server address:
        May be accessed by anyone.

Standard permission nodes are implemented.  A node for each command.  Detailed in plugin.yml

Chest detection.  When scanning for a chest to use at the post office, the postman will favor a chest with
a sign near it with the name of the post local office on it, in brackets, case insensitive.  Ie: [Bay_View]
Formerly, the postman just looked for '[mail]' on it.  The same change has been made on residential chests
used as mailboxes.  Make sure it is picked first by putting a sign near it ie:  [301_Vine_Ave].  This will
help further distinguish individual mailboxes in densely populated ares.  As a reminder, signs by
chests are completely optional.

Privileges of ownership.  Besides access to to mail and basic control of the mailbox, ownership provides the
ability to change and maintain existing routes to both address and post office owners with '/setroute'.  Post
office owners have access to the '/expedite' command for routes serviced by their post office.  Address owners
have access to '/gotoaddr' to be able to teleport to address(es) they own, possibly places where only a trusted
courier is allowed.  Of course these commands have their own permission nodes for the server administrator to
do with as seen fit.  But the contextual, owner-elevated permissions are in place.


Version 1.75

Fixed a minor command line bug and added docs for last new command /postal expedite'.

New softdepend on Vault for permissions.  Will default to Bukkit permissions
if no compatible permission manager found via Vault, or otherwise.  Vault will serve
to hook future economy support when implemented.

New permission node 'postal.admin' implemented.  Equivalent to op for administrative use.
Intended as temporary support for servers without ops.  This is the start of the formal
permissions system.

Close or lock route being edited if it is in a live editing session (/setroute).
The edited route will be automatically expedited after the edit for observation.

Fix player teleporter to place player on ground rather than a block or two high.

Defined and implement precise postmen positions.  /setlocal is where the local postman stands
in between routes.  Waypoint 0, the first waypoint on the way to an address, is the first step away
from his standing position.  The postmaster also uses this /setlocal location.  He along with the
postman uses it as the starting point for locating the post office chest.  The postmaster finds the exact
front of the chest to teleport to while the postman, as positioned by the route designer using /setlocal,
is generally a few blocks away behind his desk or partition.

On the residence end;  /setaddr, which is only used once during the route
creation process, is synchronized with the last waypoint of /setroute.  This is automatic.  The
purpose of /setaddr is to aid in the accurate naming of routes.  Hopefully, it will be easier
to remember that /setaddr must have its second parameter, the name of the address, correct and full.
/setroute expects both of its parameters to exist, and will attempt to complete them to save typing.
Both of these commands refer to the mailbox location.  Ideally, this should be the front of the
mailbox.  The idea is to make it easy for residents to change their mailbox location while making
it possible for server administrators separate route creation from route maintenance.  Only the very
end of a route needs to be modified to change a mailbox location and that is where /setroute starts
when editing an existing route.  While it is simple to redefine a mailbox location, the postman will
still find it if it is within 10 blocks of the last waypoint.

Note:  none of the above should affect existing routes.  It does make refinement possible, however.

Changed stamped player names, both author and recipient, to retain original character case in documents.
Name completion and searching is as it always was - not case sensitive in Postal commands.
Effects both /addr and /att  This completes the required infrastructure making it possible to link
live player names to mailed books.  Both sender and recipient.  The next paragraph is an example of
what is now possible.  The main use will be one of player ownership of routes and local post offices and
automatic control over who is allowed to view mail items sent to the attention of a specific player.

Mail progress announcements. Changed 'postal mtalk' from boolean on/off to 0/1/2.  Setting '0'
stops all progress announcements.  Setting '1', the default, informs only the recipient that mail
has been delivered to his/her attention, at the address it was sent to.  Setting '2' broadcasts all
mail movement.

Postman NPC checks for the occurrence of more than one postal log in a mailbox.  If true, any redundant,
correct logs are deleted. Incorrect logs are deleted.  Route changes sometimes cause cross-linked mailboxes
resulting in the postman, temporarily, servicing the wrong mailbox.  The postman tried to correct the
problem with a new postal log, but left the old one.  The issue was easily corrected, but now automatic.


Version 1.72
new command 'postal expedite' both console and player.  Allows op to push a specific route
schedule forward.

console: 'postal talk' automatically turns quiet off

Deal with the unusual situation where a waypoint needed by the NPC is deleted while editing
a route, live.

Remove dynamic waypoint attempted at residence.  This is now obsolete since /setroute now synchronizes
the last route waypoint with the residence location.  Allowing them to be set independently makes it
possible to create incorrect routing, difficult to diagnose.  Any problem finding a residence mailbox is
quickly solved using /setroute to re-set the last waypoint or two.

More work on dynamic speed control.  Incresed table resolution.  Capped off slowest at 0.4
These values should correlate with standard Citizen2 speeds when 'postal speed' is set
to 1.0  Actual NPC speed will be the average between the last waypoint segment and the current segment
multiplied by the 'postal speed' scaling factor.

switch (distance) {
    case 0:
        speed_factor = 0.40f; break;
    case 1:
        speed_factor = 0.40f; break;
    case 2:
        speed_factor = 0.45f; break;
    case 3:
        speed_factor = 0.50f; break;
    case 4:
        speed_factor = 0.55f; break;
    case 5:
        speed_factor = 0.60f; break;
    case 6:
        speed_factor = 0.65f; break;
    case 7:
        speed_factor = 0.70f; break;
    case 8:
        speed_factor = 0.75f; break;
    case 9:
        speed_factor = 0.80f; break;
    case 10:
        speed_factor = 0.85f; break;
    case 11:
        speed_factor = 0.90f; break;
    case 12:
        speed_factor = 0.95f; break;
    default:
        speed_factor = 0.999f;
}


Version 1.71
Implemented 'speed' in config.yml to scale overall walkspeed of NPC's
floating point 0.5 - 2.0
new command 'postal speed', both console and player to facilitate speed adjustment
while server is up.
tweaked door navigation.
adjusted dynamic speed table


VA_Postal
Version 1.7  11/16/2012

Citizens2 2.0.4, build 569
CraftBukkit 1.4.5-R0.1, build 2474

(both developer builds)

Re-worked for 1.4.4, now 1.4.5 MineCraft (a moving target)

General improvements to robustness, and friendliness to the user.
Some improvements to the waypoint editor.
New mail indicator, a redstone torch, removes itself when mail chest is opened.
More, but a bit of a blur - I wanted to get this up for the bleeding edge folks.
Seems very solid, but you tell me.  Thanks.


Implemented 'speed' in config.yml to scale overall walkspeed of NPC's
floating point 0.5 - 2.0
new command 'postal speed', both console and player to facilitate speed adjustment
while server is up.
tweaked door navigation.
adjusted dynamic speed table





