Scriptsize - Revision history

CraigFatman at 17:57, 9 July 2010

2010-07-09T17:57:30Z

← Older revision		Revision as of 10:57, 9 July 2010
Line 1:		Line 1:
	'''scriptsize''' <integer>		'''scriptsize''' <integer>

	~~scriptize~~ allows the user to enforce a solid buffer limit for ~~complied~~ code size without any progressive buffer increases up to that point that normally occur during ~~start up~~.		''Scriptsize'' allows the user to enforce a solid buffer limit for compiled code size without any progressive buffer increases up to that point that normally occur during startup.

	Example of normal buffer setup would be from 16384 to 32768 to 65536 [and doubles for each normal increase to buffer size].		Example of normal buffer setup would be from 16384 to 32768 to 65536 (and doubles for each normal increase to buffer size).

	Using "scriptsize #" can bypass this if you're having ~~problems~~ in-game that you suspect are linked to the normal method of code-buffer increases.		Using ''scriptsize'' can bypass this if you're having in-game problems that you suspect are linked to the normal method of code-buffer increases.

	[[Category:EDuke32 specific commands]]		[[Category:EDuke32 specific commands]]

76.188.87.235 at 12:36, 22 May 2009

2009-05-22T12:36:43Z

← Older revision		Revision as of 05:36, 22 May 2009
Line 1:		Line 1:
	'''scriptsize''' allows the user to ~~enforcer~~ a solid buffer limit for complied code size without any progressive buffer increases that normally occur during start up.		'''scriptsize''' <integer>

			scriptize allows the user to enforce a solid buffer limit for complied code size without any progressive buffer increases up to that point that normally occur during start up.

	Example of normal buffer setup would be from 16384 to 32768 to 65536 [and doubles for each normal increase to buffer size].		Example of normal buffer setup would be from 16384 to 32768 to 65536 [and doubles for each normal increase to buffer size].

	Using "scriptsize #" can bypass this if you're having problems in-game that you suspect are linked to the normal method of code-buffer increases.		Using "scriptsize #" can bypass this if you're having problems in-game that you suspect are linked to the normal method of code-buffer increases.

			[[Category:EDuke32 specific commands]]

76.188.87.235: Based on me and TX's testing of it on NR. Sorry if the format's very unprofessional right now. I just wanted to get the info about it up on here while I remembered to. :P

2009-05-22T12:34:55Z

Based on me and TX's testing of it on NR. Sorry if the format's very unprofessional right now. I just wanted to get the info about it up on here while I remembered to. :P

New page

'''scriptsize''' allows the user to enforcer a solid buffer limit for complied code size without any progressive buffer increases that normally occur during start up.

Example of normal buffer setup would be from 16384 to 32768 to 65536 [and doubles for each normal increase to buffer size].

Using "scriptsize #" can bypass this if you're having problems in-game that you suspect are linked to the normal method of code-buffer increases.