35 replies to this topic

[Kingdaro]

It's actually both. You can call functions inside tables with colons and periods - the combination in which they are defined and called usually depends on if the user wants to use the "self" keyword.

In this case though, you can do both without any problems (I think).

[Watcher7]

Also, please learn to indent your code with atleast 2 spaces (4 spaces or 1 tab is more common) per block, otherwise people can't read large scripts you make and you might get lost in your own code (and get laughed at by less understanding programmers).

Example of indentation:

local indentation = {}

function indentation.example()
	local correct = true
	if correct then
		for counter = 1, 10 do
			print('This is an example of "correct" indentation.')
		end
	end
end

indentation.example()

[brett122798]

luanub, on 07 October 2012 - 03:53 AM, said:

Not in the case of the fs api.

A good tutorial on using fs is here

Both ways work, that is currently not my problem atm. Look above. EDIT: Last Page


EDIT: Ninja'd

Watcher7, on 07 October 2012 - 03:56 AM, said:

Also, please learn to indent your code with atleast 2 spaces (4 spaces or 1 tab is more common) per block, otherwise people can't read large scripts you make and you might get lost in your own code (and get laughed at by less understanding programmers).

Example of indentation:

local indentation = {}

function indentation.example()
	local correct = true
	if correct then
		for counter = 1, 10 do
			print('This is an example of "correct" indentation.')
		end
	end
end

indentation.example()

I know, my code looks horrible, but the reason I don't is cause I think it's wasting time.

[Watcher7]

brett122798, on 07 October 2012 - 03:58 AM, said:

luanub, on 07 October 2012 - 03:53 AM, said:

Not in the case of the fs api.

A good tutorial on using fs is here

Both ways work, that is currently not my problem atm. Look above. EDIT: Last Page


EDIT: Ninja'd

Watcher7, on 07 October 2012 - 03:56 AM, said:

Also, please learn to indent your code with atleast 2 spaces (4 spaces or 1 tab is more common) per block, otherwise people can't read large scripts you make and you might get lost in your own code (and get laughed at by less understanding programmers).

Example of indentation:

local indentation = {}

function indentation.example()
	local correct = true
	if correct then
		for counter = 1, 10 do
			print('This is an example of "correct" indentation.')
		end
	end
end

indentation.example()

I know, my code looks horrible, but the reason I don't is cause I think it's wasting time.

Hitting the tab key isn't that hard nor is it time consuming.

[brett122798]

Watcher7, on 07 October 2012 - 04:01 AM, said:

Hitting the tab key isn't that hard.

You cannot tab on CC computers, and half my code was done on one.

[Luanub]

Try using io.open() and the just file:read() and see what that does. Since your storing a single word string in the file it should properly read it.

Other things to check:
What do the contents of the file look like after the write?
You can also do something like this to check what the variable type is:

sType = type(newusername)
print(sType)

Do the same thing for username.
Also print them on the screen when they are being written or read so that you can see what it is doing. That should give you an idea as to what is going wrong.

[chiloxsan]

brett122798, on 07 October 2012 - 04:05 AM, said:

Watcher7, on 07 October 2012 - 04:01 AM, said:

Hitting the tab key isn't that hard.

You cannot tab on CC computers, and half my code was done on one.

If you are playing any version under 1.4 (such as the version that is included on Tekkit), the text editor does not tab. Any version above and when you hit tab the line is indented by 2 spaces.

[Watcher7]

brett122798, on 07 October 2012 - 04:05 AM, said:

Watcher7, on 07 October 2012 - 04:01 AM, said:

Hitting the tab key isn't that hard.

You cannot tab on CC computers, and half my code was done on one.

But CC is now able to pull from your clip-board, you should not be doing anything but quick edits in-game with edit. All your work should be done outside in your editor/IDE of choice and transfered over (or edited directly if the files are local).

[brett122798]

chiloxsan, on 07 October 2012 - 04:09 AM, said:

brett122798, on 07 October 2012 - 04:05 AM, said:

Watcher7, on 07 October 2012 - 04:01 AM, said:

Hitting the tab key isn't that hard.

You cannot tab on CC computers, and half my code was done on one.

If you are playing any version under 1.4 (such as the version that is included on Tekkit), the text editor does not tab. Any version above and when you hit tab the line is indented by 2 spaces.

I'm probably gonna get flamed for this, but, I'm never updating to 1.3 or anything above, I'm sick of the horrible updates. So there is no way I'll get that feature.

[brett122798]

luanub, on 07 October 2012 - 04:09 AM, said:

Try using io.open() and the just file:read() and see what that does. Since your storing a single word string in the file it should properly read it.

Other things to check:
What do the contents of the file look like after the write?
You can also do something like this to check what the variable type is:

sType = type(newusername)
print(sType)

Do the same thing for username.
Also print them on the screen when they are being written or read so that you can see what it is doing. That should give you an idea as to what is going wrong.

Hey, thanks. io.open worked! Time to move on and get more annoying errors!

[Luanub]

So I tested it and the contents of the file are "table: 73424782".

Even though the var username was correct and was a string.

So I changed your :'s to .'s and it works like a charm. As I said before with fs you need .'s not :'s.... You're error will go away if you replace them.

EDIT:Changing to io works too since it uses :'s that you have in the code.

Edited by luanub, 07 October 2012 - 04:24 AM.

[Cloudy]

I bet you're one of those kind of people who complain if updates don't happen and also if they do.

I'm curious, what makes 1.3.2 a horrible update?

[1lann]

Watcher7, on 07 October 2012 - 04:12 AM, said:

brett122798, on 07 October 2012 - 04:05 AM, said:

Watcher7, on 07 October 2012 - 04:01 AM, said:

Hitting the tab key isn't that hard.

You cannot tab on CC computers, and half my code was done on one.

But CC is now able to pull from your clip-board, you should not be doing anything but quick edits in-game with edit. All your work should be done outside in your editor/IDE of choice and transfered over (or edited directly if the files are local).

Actually when you paste from your clipboard in cc, it only pastes 1 line of your clipboard. Unless your program is one line, it's pretty much useless to copy and paste. Also since CTRL is the key to open the edit menu, it kinda stuffs up.

[brett122798]

Cloudy, on 07 October 2012 - 08:21 AM, said:

I bet you're one of those kind of people who complain if updates don't happen and also if they do.

I'm curious, what makes 1.3.2 a horrible update?

No, I like updates not to come, unless they're good. They also cause to have modders to update their mods, and stuff like that.

All updates have had something bad ever since Beta 1.8(which is what I call "The Death Update"). 1.3 just had so many poor changes since it took like 3+ months to update, and very little good. About all changes that were made were bad because I say "If it's fixed, don't try to fix it and end up breaking it." Most additions in 1.3 I just plain didn't like except like the ender chest. Oh, and 1.4 is just as bad too. Sorry, I come from alpha(probably you too) when things were simple, yet more fun.

[Cloudy]

1.3 was a necessary rewrite to allow the modding API. Well worth it in the long run. I'm from alpha too - but I like the changes - I guess that's where we differ - but I'm off topic - bad Cloudy!

[brett122798]

Cloudy, on 07 October 2012 - 09:16 AM, said:

1.3 was a necessary rewrite to allow the modding API. Well worth it in the long run. I'm from alpha too - but I like the changes - I guess that's where we differ - but I'm off topic - bad Cloudy!

Are the clouds gonna be mad at you now? J:

Did I hear thunder?