I just reallized as I was trying to build a command maker that we're gonna need to store more than just the command in the XML code. We're gonna need a grammer context. For intstance "n torch" is dumb but so is "take" they both have bad grammer. It should be "n" and "t torch". So while n shouldn't be followed by an item t must. But the n command might be modified by run, but just run doesn't make sense. Also the commands need to know how to respond if that is imposible. for instance, when the gamer enters: "take pwnage staff" take needs to know to say: "You can't get at that." The same for directional commands, right down to run. These are probably thoughts for future updates but the compiler needs to have some idea what these commands mean.
I just reallized as I was trying to build a command maker that we're gonna need to store more than just the command in the XML code. We're gonna need a grammer context. For intstance "n torch" is dumb but so is "take" they both have bad grammer. It should be "n" and "t torch". So while n shouldn't be followed by an item t must. But the n command might be modified by run, but just run doesn't make sense. Also the commands need to know how to respond if that is imposible. for instance, when the gamer enters: "take pwnage staff" take needs to know to say: "You can't get at that." The same for directional commands, right down to run. These are probably thoughts for future updates but the compiler needs to have some idea what these commands mean.