• Announcements

    • Ashal

      SITE MOVED - IN READ ONLY MODE   12/08/2015

      Please use http://www.loverslab.com moving forward. Site has been restored to a previous version, and this one placed into a read-only mode. This is available for a limited time so users may reference/copy content that has been lost in the transition. This will no longer be accessible by December 22nd, 2015.

jaam

Contributor
  • Content count

    1,434
  • Joined

  • Last visited

Everything posted by jaam

  1. if you use "let", then NVSE will be interpreting/compiling your expression so you can reference anything that NVSE brings. On the other hand "if" or "set" will be interpreted by the vanilla compiler so they are limited to functions that return vanilla types. Except if you opted to use the Compiler Override, because in that case EVERYTHING will be interpreted by NVSE.
  2. Delete all files in your temp directory You have exceeded the maximum count of temporary files. I get this one "regularly".  
  3. NVSE

    My bad, one more thing to verify  
  4. NVSE

    I think DoctaSax did test testexpr, isn't it Doc ?
  5. If you are using a custom NPC, add all packages in GECK. AddScriptPackage can possibly fail in so many ways   Your custom NPC must support:   Interrupt package. Dialogs, comments, combat... Any package the engine can choose to add.   EVP. If you or the engine call EVP on the custom NPC, it must end up picking the package you want.   With addscriptpackage that means continuously verifying which package s running. With GECK package, you just have to make sure your conditions are correct.   Lastly your comment about addScriptPackage not checking conditions is extremely surprising. Do you have a repeatable scenario?      
  6. if not InInterior, you can call GetParentWorldspace on GetParentCell
  7. AddScriptPackage SexoutDoNothing ?   I used it with good result on scrambler in the infamous tryout scene  
  8.   There is a "compare to" function in TES5Edit that can use plugins outside of data.
  9. NVSE

    Yeah, I never realized , though it's plain in the source
  10. NVSE

    $ applies to stringVar, its an alias for ToString. Does it also work for converting integer to string ?
  11. NVSE

    ok , but why the $ ?
  12. NVSE

    IsWaiting is a vanilla function   Why do you keep prefixing your ints with $ when outputting them with print ?  
  13. Anything unknown starts as a UInt32 before being qualified In this case it would be logical though to have a list.
  14.   It also works with a form or a ref as param.   Get/SetEquipmentBidpedMask and GetPerkRank will be in the next NVSE version.
  15. Why are you converting your ints to strings ? $Rating expect Rating to be a string_var !   Otherwise all three way of calling are valid.  
  16. The Sexoutng Api (How-To For Modders)

    You should register a callback spell for when the sex is done. At that time the anim should be stopped, even the KO if I am not mistaken. In your spell script you handle the rest of your script. Though precise timing is extremely hard to predict.
  17. NVSE

    The way prideslayer and I wrote the messaging interface in NX would do that, as would any plugin based on the nvse_plugin_example.   10 is kMessage_RuntimeScriptError so it is logical relative to the error reported above. One could write a plugin that does try to work with the string parameter of the message, but I' not sure you would get more than what you have in nvse.log.   Is that done by one of your script of the debugging functions from SexoutSpunk ? Dumping Array #1232 ** Refs: 2 Owner 52: SexoutSpunk.esp [ 0.000000 ] : licked Error in script 520256fb Division by zero File: SexoutSpunk.esp Offset: 0x016A Command: Let Error in script 520256fb Operator / failed to evaluate to a valid result File: SexoutSpunk.esp Offset: 0x016A Command: Let Error in script 520256fb An expression failed to evaluate to a valid result File: SexoutSpunk.esp Offset: 0x016A Command: Let ** Given how "artistic" the way the script data is passed to the NVSE function, and the engine stripping out all EditorID during load it is hard to be more explicit. Maybe adding an HexDump of the 256 chars starting at the faulting offset ? Though you could paste the compiled script from FNVedit in an HexEditor for the same result