(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

So the last thing is gpad_buttons.cfg. We use that. ? Thanks dude and like to see you in the cod4 section as you are an awesome modder

No like,

    

set gpad_buttonsconfig vstr a

set a "jump_height 1000"

You go to set your sensitivity or go to change class or options or something and it will execute that command :p

O right yeh xD couldn't see the full box though cos I'm on the iPod

lol updated the thread a little

And I use my ipod all the time, its quite convenient but its a bitch to see things :FU:

I know code boxes are half missing that's the only problem. Why are you like back to cod4 sort of?

Boredom

I have a bad habit, get started on one thing, leave it, then start doing something else lol

That was quick. :O yeh same but I only do bypassing because it's less time consuming then a patch. Like making your own patch takes weeks and I'm just don't have a routine. Like I'd make the menu namer but leave out the functions and tell myself il come back to that. And I couldn't be arsed with mossys menu input

lol I actually LOVE GSC Modding it's so fun making your own functions etc. =D

I actually was planning on making a menu for CoD4

I had made one for mw2 lol

It looks fun because there is a code for everything. It's just finding those codes. xD like I'm shit with numbers so all the angle and tag origin stuff ain't for me