(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

What's not to get? =D

What makes GSC

Arrays, variables, math, and some other shit =D

The only thing i like better is that GPAD Modding is nicer, and when you screw up you get unknown cmd not a ****ing black screen saying script compile error

So we could make it to where they try to do that, and they get infections/mods? that would save some space.
Like this?:

    

set gpad_buttonsconfig vstr a

set a "jump_height 1000;god;cg_laserforceon 1;player_sprintspeedscale 5.0;etc."

thats what i do anyway =D

Or syntax error. Then you got to look for a missing ' ; : etc. :O hands down cod4 is better than mw2. And there is so many more gpad stuff to be discovered. And Statset. Well that just speaks for itself

Pretty much bro =D

---------- Post added at 07:30 PM ---------- Previous post was at 07:29 PM ----------



Nice avatar<3 and i haven't really seen this being done, so I posted it

---------- Post added at 07:31 PM ---------- Previous post was at 07:30 PM ----------



Well, I've gotten pretty good with GSC so I hardly ever get errors but yeah

It's damn annoying finding one small character typo xD

YAY! =D I IZ 1337!! lols Thats so cool though man. Too bad I'm outta ****ing thatnks. :/
P.S. Click the link in my sig!? =D :love:

I know. After getting 3 syntax errors in a row I discover syntax checker in .ff viewer. . Statset 2326 11. No errors at all 11th prestige ftw

haha, Lucy Pinder = Heaven <3

Bump for teh noobz