##---------------------------------------------------------------------------
@node "tech_summary"
##---------------------------------------------------------------------------
This update of the game Frontier contains several different changes, which
are in many cases unrelated, and can thus also be implemented 'standalone'.
This is done by the update implementor by reassembling the program with a
suitable selection of assembly switches set, as illustrated below.
The values shown are those used for the current release.

NEW_mandate      =	1	;Mandatory fixes  (always 1)
NEW_dispute      =	1	;Triple allegiance for disputed systems
NEW_make_ship    =	1	;Makes 3 more shiptypes available
NEW_ship_data    =	1	;Shiptype changes (Boa_bug fix etc)
NEW_crew_rules   =	1	;Extra crew can use cabins, etc...
NEW_build_BB     =	3	;Bulletin Board ad distribution
;                 ;0=>Normal_BB,  1=>improved employment,  3=>2 New ads
NEW_hype_calc    =	1	;Hyper jump/range calculations
NEW_conbin_fix_1 =	1	;Fix of 'contact binary' bug 1
NEW_conbin_fix_2 =	1	;Fix of 'contact binary' bug 2
NEW_binary_dist  =	1	;lower distr. of binary stars
NEW_gen_sys_hist =	1	;System histories (room for new subs)

NEW_drive_def    =	1	;Defines 2 new improved drive types

NEW_gen_sys_type =	1	;Star system details (economy etc)
NEW_gen_sys_star =	3	;Primary star type distribution
;		;0 = normal  1 = nice&safe  3 = wild

In addition to the changes mentioned above, there is another, which I do not
consider optional.  This is that Frontier now will always use the directory
where it was started as the initial default directory for loading or saving
commander files, even if that is on a drive not available in the short drive
list normally supported by the old Frontier implementation.  As I see it,
this change is essential to meaningful use of Frontier on a modern system.

NB: Editor programs used to modify commander files will remain compatible,
1:  except that they can't handle all new stuff, and will mistake the codes
    for the drive types beyond 'Class 7 Hyperdrive'.  This is harmless, and
    the programs may still be used, as you can easily figure out which drive
    types actually correspond to the ones stated by such an editor program.

NB: Old commander files using Military drive types will not work properly
2:  with the new Frontier game engine, as the drive codes have changed.
    For the same reason it is not advisable to use commander files using
    either Military drives or any of the new ships and/or drives  with
    the old Frontier game engine.  Doing so may cause a system crash.

##---------------------------------------------------------------------------
@endnode "tech_summary"
##---------------------------------------------------------------------------
