Considering writing a QuakeC/Modding tutorial

I did start writing a beginner's guide. Rather than hemming and hawing over what editor to recommend, I started with chapter 2, an introduction to what the most important/commonly used source files do (progs.src, defs.qc, subs.qc) while covering basic syntax encountered at the top level (globals and fields, builtins, and function definitions)
 
I did start writing a beginner's guide. Rather than hemming and hawing over what editor to recommend, I started with chapter 2, an introduction to what the most important/commonly used source files do (progs.src, defs.qc, subs.qc) while covering basic syntax encountered at the top level (globals and fields, builtins, and function definitions)
As a total beginner I found Atom really approachable FWIW. I still use it, although I am slowly migrating to VSCode.
 
As a total beginner I found Atom really approachable FWIW. I still use it, although I am slowly migrating to VSCode.
FTE has a GUI and I find it is pretty awesome to just write it there, there are some syntax packages for other editors but I found the integration non existent. It's nice to be able to write something and compile it immediately and carry on.
 
FTE has a GUI and I find it is pretty awesome to just write it there, there are some syntax packages for other editors but I found the integration non existent. It's nice to be able to write something and compile it immediately and carry on.
The all white UI hurts my eyes after a few minutes, and you cannot resize the UI. Otherwise I'd use it. Atom is a nice grey / dark theme. Accessibility matters to some people.
 
  • Like
Reactions: Gibbon
I like the configurability of VS Code, and use the following definition for QuakeC projects:

Code:
{
    "files.associations": {
        "*.qc": "quakec",
        "progs.src": "quakec"
    },
    "files.encoding": "utf8",
    "[quakec]": {
        "files.encoding": "windows1252"
    },
    "editor.insertSpaces": true,
    "editor.tabSize": 4,
    "files.trimTrailingWhitespace": true,
    "[markdown]": {
        "files.trimTrailingWhitespace": false
    }
}
 
I like the configurability of VS Code, and use the following definition for QuakeC projects:

Code:
{
    "files.associations": {
        "*.qc": "quakec",
        "progs.src": "quakec"
    },
    "files.encoding": "utf8",
    "[quakec]": {
        "files.encoding": "windows1252"
    },
    "editor.insertSpaces": true,
    "editor.tabSize": 4,
    "files.trimTrailingWhitespace": true,
    "[markdown]": {
        "files.trimTrailingWhitespace": false
    }
}
I didn't know about this! I'll check it out.