XyliGUN

Can you share m + xy files with this event, so I can verify?

Sorry, it's been too long since I last made one of these mistakes, but it should be easy to testbed.

• \e - environment area (note: 0 - gravity, 1 - temperature, 2 - radiation)
  
• \E - environment area value (seems to be in clicks from the left?)
  
• \F - ship id (the same as fleet id)
  
• \g or \G - currently exported as an integer value, but it wasn't found in any of the m files
  
• \i - signed integer value
  
• \I - change type (0 = decreased, 1 = increased)
  
• \j - zero based research area id (0 - energy, 1 - weapons, 2 - propulsion, 3 - construction, 4 - electronics, 5 - biotechnology)
  
• \k - technology id (4 bytes unsigned integer), stored in format: bits 0-15 is an ItemId, bits 16-31 is a GroupId
  
• \l, \L or \Z - zero based player id
  
• \m - cargo type (note: 0 - ironium, 1 - boranium, 2 - germanium, 3 - colonists, 4 - fuel)
  
• \M - mine field type (0 - standard, 1 = heavy, 2 - speed bump)
  
• \n - this param consumed 2 args, it specifies location (can be either planet id, fleet id or space coordinates)
  
• \o or \s - zero based fleet id
  
• \O - zero based owner id (the same as player id)
  
• \p - zero based planet id (note: you have to add 1 to match a planet id as it shown in Stars!)
  
• \P - percent value
  
• \S - packet origin (the same as player id)
  
• \v - 4 bytes unsigned integer value (note: some events treat it "as is", some add '00'/'kT'/'mg')
  
• \V - 4 bytes unsigned integer value, but comparing to \v it always used as is, since it is already multiplied by 100
  
• \X - strange, but \X is always replaced by empty string in any event message, will be stored as empty Arg in export
  
• \z - design id (bits 0-4 - design id, bit 5 values: 0 - ship design, 1 - starbase design)