[CF-Devel] python plugin trigger bug?

[crossfire-devel at archives.real-time.com]

for starters I'm going to try changing the event trigger in the
move_apply function,

just by changing the params to:

CFP.Value[1] = victim;
CFP.Value[2] = trap;
CFP.Value[3] = originator;

The script I put up before seems to be working now.  Your table helps a
lot too and I think it should go into the python plugin docs.

>
     
      I don't think that it would be very hard to change the code: the events
     
     >
     
      in different lines in the event table are generated in different places
     
     >
     
      in the code. Therefore we can adjust them independently.
     
     >
     
     
     >
     
      Note that I think we should change the server code, not the plugin code:
     
     >
     
      the server code fills a CFParm structure and passes it to the plugin
     
     >
     
      code. This structure basically says which objects should be
     
     >
     
      Activator/WhoAmI/Other. Therefore it would be easy to adjust it in the
     
     >
     
      server code but (very) hard to do it in the plugin code because the
     
     >
     
      plugin code can't distinguish between (for example) the there different
     
     >
     
      kinds of trigger events.
     
     >
     
     
     >
     
      ______________________________________________________________________
     
     Yes, I did mean changing the event code which passes the params to the
plugin, but what I meant by changing the plugin code was that the plugin
may have to change in places to compensate for these changes...


_______________________________________________
crossfire-devel mailing list
     
     crossfire-devel at lists.real-time.com
     
     
     https://mailman.real-time.com/mailman/listinfo/crossfire-devel