Mhs: Difference between revisions

From EDukeWiki
Jump to navigation Jump to search
Plugwash (talk | contribs)
No edit summary
 
Plugwash (talk | contribs)
No edit summary
Line 1: Line 1:
with the eduke 2.1 test team releases matteus (perhaps under presure from 3dr) introduced a system of precompiled cons encrypted using the contents of the duke3d.idf file on the cd.  this code was fairly buggy and broke at least one seeminngly unrelated item the [[defaultvisibility]]. After the source release of 2.1 the encryption code was rapidly stripped out but other issues with the mhs system remained and many still belive it was a pointless idea in the first place. Also it will undoubtablly cause compatiblility problems with the wide range of ports around.
with the eduke 2.1 test team releases matteus (perhaps under presure from 3dr) introduced a system of precompiled cons encrypted using the contents of the duke3d.idf file on the cd.  this code was fairly buggy and broke at least one seeminngly unrelated item the [[visibility|DEFAULTVISIBILITY]]. After the source release of 2.1 the encryption code was rapidly stripped out but other issues with the mhs system remained and many still belive it was a pointless idea in the first place. Also it will undoubtablly cause compatiblility problems with the wide range of ports around.

Revision as of 06:30, 10 January 2005

with the eduke 2.1 test team releases matteus (perhaps under presure from 3dr) introduced a system of precompiled cons encrypted using the contents of the duke3d.idf file on the cd. this code was fairly buggy and broke at least one seeminngly unrelated item the DEFAULTVISIBILITY. After the source release of 2.1 the encryption code was rapidly stripped out but other issues with the mhs system remained and many still belive it was a pointless idea in the first place. Also it will undoubtablly cause compatiblility problems with the wide range of ports around.