Module Development > The Forge - Mod Development

More Python Troubles

<< < (3/3)

svaucher:

--- Quote from: Riven on January 10, 2007, 08:27:35 PM ---Sorry for the double-post; I have to be sure someone's going to look. Because I'm shallow like that.

When I do alt-x now in module_triggers, it shows me something I didn't even touch and tells me that my indentation is wrong. Then, though, I 'untabify region', like they tell me to, and get that beep that alerts me that something didn't take, and alt-x brings up the same error. What am I doing wrong?

--- End quote ---

Didn't see this post before my response. I'll repeat myself, you didn't close a statement, list ->
you are missing a } or a ].

Try removing parts of your dialog code and re-indent. When it works, you've identified the part that contains an error.

Hellequin:
Winter - Oh, I know I'm correct about the factual stuff.  The guesswork is that this is, in fact, the source of his problems. :P

Riven:
Arg. Now it's turning up an error in module_triggers (I think that was it; not in a position to go check right now) that says I need a float argument somewhere? Any ideas?

svaucher:

--- Quote from: Riven on January 15, 2007, 11:56:00 AM ---Arg. Now it's turning up an error in module_triggers (I think that was it; not in a position to go check right now) that says I need a float argument somewhere? Any ideas?

--- End quote ---

Another hunch, you are probably lacking an argument for a trigger. At some point the build module expects to see a number, but probably see a series of operations ( [<op_1>,<op_2>,...,<op_n>] instead of a number.

Remember every trigger has the following format:

(<number>, <number>, <number, or constant>, [<condition>], [<ops>]),

check the line mentioned, it should be relatively specific.

Navigation

[0] Message Index

[*] Previous page