It is just an opinion. Don't need to get worked up about it. I admire your experience in your profession. You should try learning about AI programming(it exists damn it!
).
I wouldn't call it AI, if it doesn't do anything unexpected. AI design is creating techniques that allow these artificial systems to respond to unexpected situations. Don't think about unexpected codes, whoa what is it? Skynet! We are talking about game AI here. As a programmer maybe you can contribute about what can be done to make this game's AI better instead of advocating scripts(as in scripted events which any gamer should be familiar so I wouldn't have to post links, not as in scripting/coding/programming) to maximize profits.
PS. You might be a good programmer but what you do is being captain obvious. In an
artificial intelligence conversation saying "AI is abstract, it is not real. It is for making it seem intelligent!!" is being captain obvious and an insult for everyone's intelligence here. I almost thought you were flame baiting first. :confused:
You know? I am not saying this to be condescending or anything, seriously, I am at fault here for basically not specifying what I mean. There are certain terms that have certain meaning to me and within my working environment, but that may have other meanings outside what I do, or my environment, or the perception of them is different.
And yes, I must admit, I do tend to get on my high horse when talking about things like coding. So I am sorry if at any time it seemed I was trying to insult anyone.
I guess the misunderstanding here is the use of the word "scripting" ... to me, whether is called scripting, or coding, it is all the same thing: it basically means a series of instructions that you execute in a certain fashion to achieve a desired result, and this desired result could very well be randomness, the effect of making and NPC seem to make a decision, etc.
However, even within my work environment, the use of the word "script" can be taken to mean different things depending on the context of the conversation: it could be that we are making the distinction between a set of code that gets compiled into a binary versus code that is on a plain text file (which is most commonly referred as a "script"), or that we are talking about a detailed step-by-step procedure, or a utility comprised of a series of scripts and maybe even binaries, or the logic within the instructions...
There is also the matter of thinking in terms of coding instructions to achieve a result, whether it is a specific routine, or something that does one thing one time, another thing another time, or at different times. The best example I can give you, is the example I always give people at work when I hit a wall
. I tell them:
"Take this dollar, go to go to the vending machine in the breakroom, get yourself a soda, and come back, then describe what you just did". Most people just respond "I went to get a soda"... some repeat verbaitm what I told them... some try to get smart, and start with " I got up, opened the door, walked to the breakroom, put the money in the machine, retrieve my soda, walked back to the room, sat down'.
Now, what is my version of the event, if I were coding it or scripting it,or let's just say creating the instructions for the event?
You handed me a dollar. I had to recognize you were giving me a dollar. I had to decide which arm I extended to reach for the dollar. I grabbed the dollar. Once in my grasp, I had to decide whether to put the dollar in one of my pockets, lower my arm, or just keep my arm static at the same position as the moment I grabbed the dollar. If I decide to put the dollar in a pocket, I need to decide which pocket. Once I make sure the dollar is in my pocket, I need to recognize I need to get up off my chair. I have to figure out if I am sitting with my legs under the table, or not. If I am not, lean forward and push with both legs to get up. If under the table, push first with my legs away from the table; do I hit a wall behind me?... well, by now you get the idea. And we are not even close to reaching the door, never mind reaching the soda machine, then figuring out if I had enough money, deciding where to put the money (coin slot or bill slot), which soda to choose, etc etc etc
And that right there, in a nutshell, if you can all that diatribe a nutshell, is how I think when I talk "scripting" or 'coding instructions". And I just can't help it
And I am sure Beth devs go through something very similar when it comes to coding "A.I." (I'm still putting it in quotation marks
)
And again, I really didn't mean to flame, or insult.. I just may get a little bit passionate about coding.. after all, I am a professional geek, that's what I do