RiiakShiNal wrote:sweetLu wrote:And to you programming professionals out there, what would coding cards be considered? Is it actually coding? Scripting? Just modding?
Well, there is some mixture here as
Modding is somewhat of a catch-all for modifications to a game or program (as such this can't really be a simple answer). So everything we do in relation to modifications for DotP is
Modding even if it could fall into different more specific areas. Though there aren't many hard fast rules as to what falls under what, especially as the lines become more and more blurred in the current state of the world.
As for
coding cards that would generally be considered
scripting as we are using a
scripting language and we are not creating a stand-alone program or library. The code we write for cards is never actually compiled, it is simply interpreted by the program it is designed to run within. However, scripting is a form of coding (a.k.a. programming) and can also be considered such. Most card coding changes fall under scripting, though since mods also contain art for the cards and/or other resources a single WAD would often more appropriately fall under modding rather than just scripting.
Creating stand-alone tools such as thefiremind's
Web Generator or my Deck Builder would be more considered
developing as we control the source code to those tools and they don't run within the confines of another program. With developing we have considerable control and freedom to make what we want. Generally, stand-alone applications are compiled separately (though not always true for web applications) and require a compiler to generate the application code from the source. Again developing is often a form of coding and can also be considered such, though developing can also apply to other things that don't involve code.
Patching something can fall into different categories depending on how the patch is done. For example Rick's patcher for the DotP games is a separate library and would be considered along with developing. Though patching of some of the standard Lua functions we are given would be considered within scripting as it would be along the same lines as coding for cards (even if the patch were for a menu function or other area).
Some changes that are made to a game such as modifying images or other graphics would not be covered under scripting, developing, or coding, but still could be covered under
modding as we would be altering the resources the game uses. Depending on the modifications being done it could even be considered under
graphic design.
Fantastic explanation of it

This is why I always go with modding, because no matter what it falls under otherwise, modding works for all of it. It doesn't
really fit for the deck builder, the tools for the CW, or TFM's generators, but because they're so focused on one game, I don't feel guilty using the term there, too.
I almost always using scripting to explain what I'm doing, but I use coding when talking about a specific card. By that I mean I would answer "What are you doing, now?" with "I'm scripting" or with "I'm coding a card(s)." And for Skyrim, which I also mod, I almost always go with scripting because that's the VAST majority of what I do when modding it.
I must admit, while most of what you said is what I was already thinking, I didn't know about the origin of the term scripting. That makes sense and I'd been curious about it.
Creating stand-alone tools such as thefiremind's
Web Generator or my Deck Builder would be more considered
developing as we control the source code to those tools and they don't run within the confines of another program. With developing we have considerable control and freedom to make what we want. Generally, stand-alone applications are compiled separately (though not always true for web applications) and require a compiler to generate the application code from the source. Again developing is often a form of coding and can also be considered such, though developing can also apply to other things that don't involve code.
This is why I kept flip-flopping internally with how to refer to the utilities I was making for the CW. It's kind of a system of its own, deserving the 'developing' term. It's kind of just a bunch of scripts, deserving only the 'scripting' term. It's definitely 'coding', but that's kind of a cheat since it's more of a general catch-all. I eventually went with 'scripting' because while 'development' could mostly fit, I never compile anything (or at least, nothing that can't
very easily be decompiled, and the script I make isn't even compiled in the program, it's stored as plain-text), and also, to me, developing kind of implies some sort of work other than just coding: UI design, graphic design (
for the UI design), database creation/maintenance,
something. I decided to just go with scripting.