Jump to content
  • Announcements

    • AndalayBay

      Orphan Attachments   07/31/2018

      I have been doing some housekeeping lately and I've noticed that I had a lot of orphaned attachments. Attachments get orphaned when the PM or post is deleted without removing the attachment first. Deleting a PM or post does not delete the attachment and the file or image remain on the server. I'd like to ask all members to go through their attachments and delete any attachments you don't need anymore or those that have been orphaned. Where can I get a list of my attachments? Click on your display name in the upper right corner of the forums and pick "My Attachments" from the drop-down list. How can I tell an attachment is orphaned? If the PM has been deleted, you'll see a message like this in your attachment list: Unfortunately there is no message if the post has been deleted, so please check your old posts. We do purge old birthday threads every once in a while. Also some hosted projects have been shut down, so you may have orphaned attachments on one of those locations. Thanks!

Ervvin

Members
  • Content count

    4
  • Joined

  • Last visited

  1. WIP halted by OBSE Compiler

    @Malonn, thank you. I tried some more tests. There are many of these Package Flag Commands in OBSE: SetPackageOffersServices, SetPackageMustReachLocation, SetPackageMustComplete, etc, etc. According to the documentation, syntax is identical for all of them. I tested most of them, and always got the same error message, cited in the 1st post. However, a quick test of SetPackageTarget (syntax per OBSE doc: SetPackageTarget package:ref targetReference:ref) with SetPackageTarget zz1Chor1CaptainGoForIt ChorrolWellMarker is silently accepted by the compiler. The package is recognized! So if the Documentation is correct, I assume these flag commands are buggy. If there is a doc error, then CSE may shed light on it - but I'm not using that yet... I tried it once, loved its looks and interface, but argh, it wants Admin rights for the CK! Why? Never mind, I'll get used to it I suppose... later, not now, because I'm in the middle of this very complicated mod That Will Shatter The World, and I'm afraid to get distracted
  2. WIP halted by OBSE Compiler

    @Vorians - OBSE documentation: "Commands which modify AI packages operate on the base package and may have no effect or unpredictable effects on actor references currently executing that package." I guess that would mean the ref must be an Editor ID. BUT I didn't consider the 2nd part of that sentence before now... why would I want to use SetPackageAlwaysRun when it's so unreliable? My NPCs run those packages constantly, so the workaround suggested by AndalayBay may be better anyway. Thanks, both of you.
  3. WIP halted by OBSE Compiler

    The new Bethsoft forum for Oblivion modding is dead. Besides, Skyrim may be a good game but I don't like it enough to want to mod for it. One playthrough was more than enough. I'll think about workarounds for my script problem. Thanks for your reply
  4. WIP halted by OBSE Compiler

    Greetings, Anyone know if the OBSE authors still take bug reports, let alone maintain their prog? If they do, then where do I go? Couldn't find any forum thread of that nature, alas. (On that note: where is the old gang that used to live in the BethSoft mod forum? Is this site the new hangout? Yes, I quit some 8 years ago, recently started to play and mod Oblivion again, but 'everybody' seems to have moved on. Except good old WalkerInShadows, thank god and the few familiar sounding nicks in this forum) Anyway, could someone please tell me I'm doing something wrong? I'm not a very confident programmer: Begin OnPackageDone zz1Chor1CaptainGoForIt ..... ..... ..... SetPackageAlwaysRun zz1Chor1CaptainGoForIt 0 Both lines are in the same script, where the 1st line works OK, but the compiler chokes on the second, saying "Unknown variable 'zz1Chor1CaptainGoForIt' for parameter int." IMO there is no int in that line, just a ref and a bool. Thoughts? Thank you. Edit: ugh, that code box, sorry. Can't figure out what went wrong.
×