Structuring the code in the LUA files

Garry's Mod coding
#1

Hey Facepunchers!

I’m trying to edit some LUA files that I got from a gamemode just for fun but I find it really hard to get a nice structure on the code since all of it is just moshed together in a big mess.
Is there any way to structure the code in the LUA files easily?

#2

If you’re talking about how you should whitespace your code, this is how I do it. If you’re going to structure already existing code, you need to probably use search & replace.

[lua]
function SomeFunction(args, stuff, moar)
if(stuff == true) then
print(args, stuff, moar);
else
print(“Too bad”);
end

player.GetAll()[1]:ChatPrint("Hey");

end

SomeFunction(“I”, true, “like pie”);
[/lua]

#3

You forgot Tabs!
[lua]
function SomeFunction(args, stuff, moar)
if(stuff == true) then
print(args, stuff, moar);
else
print(“Too bad”);
end

    player.GetAll()[1]:ChatPrint("Hey");

end

SomeFunction(“I”, true, “like pie”);
[/lua]

#4

i hope this isn’t the way you indent your code

#5

Ugh, my browser messed that up.

#6

Hey, thanks for the reply!
I’m very new with this, I just want to add some things to the code of a gamemode but I can’t really find a pattern in the code since it’s just messed up. I’m trying to edit the init.lua file but the code is really long in a very few rows, I want to get the code easier to read somehow.
Can I ask what program are you using when you’re editing code etc? I just use the notepad lol, I guess you’re using something else xD As I said, I’m a big newbie to this.

#7

Notepad ++

#8

Use Notepad++ with the GM10Lua plugin and don’t indent your code like DarKSunrise. Do it like Commander204.

edit: but don’t put ;'s after each line that is fucking gay

#9

Okay, thanks! I’ll try it now.

[editline]04:28PM[/editline]

Haha okay! Thaks a lot guys, I’ll start googlin’ right away! ^^

#10

Whenever someone asks me about coding ethics, I always tell them the ten commandments of Lua scripting that I follow:

1.) For every function, thoust must end it.
2.) For every if-statement, thoust must end it.
3.) For every do-statement, thoust must end it.
4.) Thoust shall tab everything inside a function.
5.) Thoust shall tab everything inside an if-statement.
6.) Thoust shall tab everything inside a do-statement.
7.) Thoust shall leave a blank spot between function blocks
8.) Thoust shall block code of a similar intent
9.) Thoust shall keep simple statements in a single line (if not Var then Var = Value end)
10.) Thoust shall always optimize

#11

how does it feel being a giant tool

#12

Sounds great! Thanks for the advice! :smiley:

#13

How does it feel being a giant cunt?

To answer your question, great. Whenever someone needs help tightening a bolt, I don’t even need to go grab my toolbox.

#14

Haha, n1.

[editline]04:46PM[/editline]

Come on, he just tried to help ^^

#15

Don’t use any kind of NP++ plugin that shows you the functions, I have never have. You don’t really need to… or maybe I’ve just been coding Lua for GMod for so long that I know everything off by heart… oh how sad.

#16

I’ve never bothered with it either. If you’re unsure of a function, just look it up on the wiki…

#17

Haha lol, okay :stuck_out_tongue: I don’t use any plugins at all.

[editline]05:41PM[/editline]

Okay, I’ll do that! Thanks.

#18

Or use Overv’s awesome search thing. I love it because it shows the arguments, in the search itself.

#19

Okay, I’ll check it out. Thanks!

#20

I really suggest you use this plugin http://www.facepunch.com/showthread.php?t=477505

It will make finding syntax errors and reading your code much more easier.