(adsbygoogle = window.adsbygoogle || []).push({}); Well, I've been seeing people posting codes and whatnot so yeah, might as well teach how to save a bit of space even though this is old and many people probably know this :sleep:

Okay, first off, there is no need for quotes.

Ex.

    

set blabla "1"

can just be

    

set blabla 1

And don't be afraid to put in other things while in there!

Such as vstr etc.

I think that when you have more than one thing though, you must enclose it with quotes.

like

    

set "vstr a;jump_height 1000;vstr blabla"

Also, one confused thing, is that people for some reason think that they can put things from GSC Scripting in GPAD Modding /facepalm

That is oh so wrong. Very very wrong.

GPAD Modding != GSC Modding

You cannot remove whitespace in a similar fashion as GSC.

What you CAN do is not space everything out all the damn time.

    

set "jump_height 1000 ; vstr a ; set a vstr a1 ; say ^8Damn"

can be

    

set "jump_height 1000;vstr a;set a vstr a1;say ^8Damn"

Also, instead of using say, just do the unknown cmd trick to print text

like

    

say ^6asdf

Could just be

    

^6asdf

Remember, when using that trick, for 3 or more words, you must bind the word with underscores.

so this would not work

    

set a "asdf ass asdf"

You would neeed to put either

    

asdf ass

or

    

asdf ass_asdf

Anything in the same line will read it as the same command.

Also, don't ALWAYS use vstr. Just because you want it to look fancy will cost you valuable space. You have exactly 1024 bytes in the GPAD0 files.

Don't be afraid to cross codes. I mean, vstr doesn't have to be in the same GPAD0 file. It also doesn't matter which codes go in which.

Also, when you bind something, then bind it to something else that bind gets overwritten (jokes)

Another downfall is that you cannot use any type of math in GPAD Modding. Except variable strings (vstr).

If you could, that would save so much space.

Also, use exec WHENEVER you can. Very good things there.

And when you can, instead of putting Press Right to do this, hex edit it to show the button.

like God Mode = 11 (hex edit the 11 to show whatever button)

And don't put super long names for vstr. like set z0mglolwtfbbq ^1asdf, instead use something like set 1 ^1asdf

And that's about all the advice I have.

Oh! One more thing, you can set your gpad_buttonsconfig to a certain command you would like to execute when you go in the menu (pretty darn old but forgotten)

Anything else anyone wants to share, feel free and I will add it to the thread

Thanks for reading :p

Dunno . Getting rid of TRH but monkey-bomb is who I am . How much is it to edit your title :confused:

You can't change your title unless your premium. :/

Agh right. Well I'm killing TRH (my old clan). !!MONKEY-BOMB!!

exaclty like me, i think i've created about 2 patches for cod4 but cba to finish them ha =D

Me three. I would have some HUGE rep and post count here, but I have the shortest attention span in the world lol.

Also, you only need this in the cm:

    

set gpad_buttonsConfig asdf

and you don't need anything in the mp. Also the only time you need quotes is for binds. Another way to save space is to not make realistic mod menus. We created the vstr menu not because it looked good, but because it allowed you to add more binds. Also save space with say commands by changing you text from "Press right on the dpad for god mode" to "<=God"

The Last method I have to save space is to make your vstr commands short. Don't do

set ThisIsTheFirstMenu "blah blah blah"

do

set 1 "blah blah blah"

Actually you don't but like I said, you can link that to a certain command :y: