-
Notifications
You must be signed in to change notification settings - Fork 13
Configuration File Standard #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
From what i can see your using |
|
Hmm, that's true, let's see what other people thing. |
Nearly forgot about that
|
ComputerCraft Introduced an Standard itself, using your Standard is like using something else instead of Rednet (but with modems too) |
|
@Luca0208 a couple of things:
|
|
1.I'm not good with name, everyone feel free for suggestions |
|
To be honest I think config files should just use |
|
My point is, if someone who is new to CC sees these two files(can't use codenlocks currently, sorry): and {
Name="Player1",
Difficulty=1,
}The potential to screw up the bottom version is higher.
|
|
In that case, you are better off making a GUI settings screen. Nice people make those even for experienced users, so that they don't have to dig through the config files. I feel like closing this because #41 is superior. Any objections? |
|
Yes, this should be closed in favor of #41. Intentionally not supporting line breaks isn't fantastic, and valid-lua configuration files are easier to handle than plain text, within the context of ComputerCraft. |
No description provided.