Not to be rude, I'll reply to myself on this - when I switch the calling object from a pedestal to a button I get the following error: The unknown trigger type error maybe seems to indicate that the hook has tried to pass the player as the trigger object... PYTHON - HandleEvent:: got script file > /python/guilds/guild_pedestal.py< -1073745037 Unknown trigger type: Avion (1) PYTHON - HandleEvent:: script loaded (/python/guilds/guild_pedestal.py)! PYTHON - triggerEvent:: eventcode 10 PYTHON - HandleEvent:: got script file > /python/guilds/guild_pedestal.py< Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 13108)] find_event (op=0x0, etype=10) at loader.l:1855 1855 for(found=op->events;found!=NULL;found=found->next) On Sat, 2004-12-04 at 17:32, Todd Mitchell wrote: > Hmmm, > > everytime I hook a pedestal to a python script with the trigger hook I > get a segfault. The python script doesn't seem to matter - even if it > does nothing it still segfaults - is there something in the trigger hook > that is broken? > > Here is the GDB error I get. > > > 0x080a4da3 in update_button (op=0x8a52b48) at button.c:187 > > 187 (!strcmp (tmp->slaying, "player") && > > > > _______________________________________________ > crossfire-devel mailing list > crossfire-devel at lists.real-time.com > https://mailman.real-time.com/mailman/listinfo/crossfire-devel _______________________________________________ crossfire-devel mailing list crossfire-devel at lists.real-time.com https://mailman.real-time.com/mailman/listinfo/crossfire-devel