Mhs - Revision history

Hendricks266 at 16:39, 21 March 2012

2012-03-21T16:39:41Z

← Older revision		Revision as of 09:39, 21 March 2012
Line 1:		Line 1:
	With the EDuke 2.1 test team releases [[Matteus]] (perhaps under pressure from 3D Realms to improve the CD copy-protection) introduced a system of precompiled cons encrypted using the contents of the SUPPORT\DUKE3D.IDF file on the CD. This code was fairly buggy and broke at least one seemingly unrelated item, [[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 believe it was a pointless idea in the first place. Also it will undoubtedly cause compatibility problems with the wide range of ports around.		With the [[EDuke]] 2.1 test team releases [[Matteus]] (perhaps under pressure from 3D Realms to improve the CD copy-protection) introduced a system of precompiled cons encrypted using the contents of the SUPPORT\DUKE3D.IDF file on the CD. This code was fairly buggy and broke at least one seemingly unrelated item, [[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 believe it was a pointless idea in the first place. Also it will undoubtedly cause compatibility problems with the wide range of ports around.

	EDuke32 is 2.0 based and [[TerminX]] has not added support for the mhs system.		[[EDuke32]] is 2.0 based and [[TerminX]] has not added support for the mhs system.

Hendricks266 at 16:39, 21 March 2012

2012-03-21T16:39:31Z

← Older revision		Revision as of 09:39, 21 March 2012
Line 1:		Line 1:
	~~with~~ the ~~eduke~~ 2.1 test team releases ~~matteus~~ (perhaps under ~~presure~~ from ~~3dr~~ to improve the cd protection) 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.		With the EDuke 2.1 test team releases [[Matteus]] (perhaps under pressure from 3D Realms to improve the CD copy-protection) introduced a system of precompiled cons encrypted using the contents of the SUPPORT\DUKE3D.IDF file on the CD. This code was fairly buggy and broke at least one seemingly unrelated item, [[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 believe it was a pointless idea in the first place. Also it will undoubtedly cause compatibility problems with the wide range of ports around.

	~~EDUKE32~~ is 2.0 based and ~~terminx~~ has not added support for the mhs system.		EDuke32 is 2.0 based and [[TerminX]] has not added support for the mhs system.

Plugwash at 16:48, 26 August 2005

2005-08-26T16:48:39Z

← Older revision		Revision as of 09:48, 26 August 2005
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 [[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.		with the eduke 2.1 test team releases matteus (perhaps under presure from 3dr to improve the cd protection) 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.

			EDUKE32 is 2.0 based and terminx has not added support for the mhs system.

Plugwash at 13:30, 10 January 2005

2005-01-10T13:30:48Z

← Older revision		Revision as of 06:30, 10 January 2005
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.

Plugwash at 13:29, 10 January 2005

2005-01-10T13:29:58Z

New page

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.