Jump to content

Daeros_Trollkiller

Modders
  • Posts

    224
  • Joined

  • Last visited

Posts posted by Daeros_Trollkiller

  1. On 5/5/2024 at 3:06 AM, DrAzTiK said:

    it can works but it will never be as good as a real native controller support  imo .   (no wheel and no way to control characters the way you can do in bg3)

    Dragon age origin (pc version) is quite decent with JoytoKey

    No doubt there.  That's why I brought up Steam input if that's an option.  It's much more user-friendly, imho, since you can save controller profiles (and even share them with the steam community), once you get a config you like for a game, you can save it, and always have it handy even if you upgrade to a newer PC, or have to reinstall things.  I just wish Valve would release a new standalone steam controller based on the controls for the Deck.  I've fallen in love with it's layout and capabilities.   It's the only modern controller layout for me that I can manipulate d-pad controls and analog controls in a way that feels natural and comfortable.  I know that's totally a subjective thing, but still...

  2. JoytoKey is probably going to be your best bet:

    https://joytokey.net/en/

    If you are playing through steam, check out the community controller profiles for the game, that might make it much easier for you than trying to do it manually.   Just enable steam input for the game from options->properties->controller and go to town. 

    I absolutely love this feature on my Steam Deck.  Makes setting up gamepad controls for PC games that don't have support (or modern controller support), a breeze.  Heck, I managed to play through Ultima 6 on it this way.

  3. I have another one I wanted to run by you more experienced folks:

    This one involves me trying to use a new trigger to have the genie in trademeet reward a SoD scimitar in place of the normal one.  Everything works, just want to see how COPY_TRANS would apply here, if it's needed, or something else altogether:

    EXTEND_BOTTOM TRGENI01 35
    
    IF ~Global("BD_HAVE_SOD","GLOBAL",1)
        Global("K0_SOD_IMPORT_30","GLOBAL",1)~
    
    THEN DO ~GiveItemCreate("bdsw1h08",LastTalkedToBy,0,0,0)
             SetGlobal ("K0_SOD_IMPORT_30","GLOBAL",2)~ GOTO 36
    END
    
    EXTEND_BOTTOM TRGENI01 39
    
    IF ~Global("BD_HAVE_SOD","GLOBAL",1)
        Global("K0_SOD_IMPORT_30","GLOBAL",1)~
    
    THEN DO ~TakePartyItem("misc8k")
             GiveItemCreate("bdsw1h08",LastTalkedToBy,0,0,0)
             SetGlobal ("K0_SOD_IMPORT_30","GLOBAL",2)~ GOTO 36
    END

    And regarding COPY_TRANS.  What if all I want to do with a transaction is add a new trigger that routes to a new state that includes everything from the original, and just adds a new string to it?

    For instance here:

    IF ~~ THEN BEGIN 54 // from: 53.0
      SAY #36309 /* ~Your place is here whenever you wish it, even if you do not actively serve. Remember that you remain in the gaze of the Vigilant One, and that your actions reflect upon him. Go with honor.~ */
      IF ~~ THEN DO ~AddexperienceParty(35000)
    GiveGoldForce(1000)
    SetGlobal("Talonwar","GLOBAL",3)
    EraseJournalEntry(55617)
    EraseJournalEntry(55619)
    EraseJournalEntry(55621)
    EraseJournalEntry(55622)
    EraseJournalEntry(55623)
    ~ SOLVED_JOURNAL #55618 /* ~Cleric stronghold: Halting the Talon war
    
    I have served the greater law and pacified both the Talons and the followers of the Morninglord. My service to Helm has been recognized as invaluable. For now, I have been released from further service as a boon for all that I have done so far. I await to be called if need be.~ */ EXIT
    END

    What I would like to be able to do here is have an additional trigger:

    IF ~Global("BD_HAVE_SOD","GLOBAL",1)
        Global("K0_SOD_IMPORT_46","GLOBAL",1)~

    which would do the below in addition to what normally happens, without any additional SAY's and such:

    THEN DO ~GiveItemCreate("bdblun09",LastTalkedToBy,0,0,0)
    SetGlobal ("K0_SOD_IMPORT_46","GLOBAL",2)~

    If such a thing is even possible to do in a way that doesn't cause issues for other mods.

  4. Thank you for the feedback, Jastey.  Could you expand more on what you mean on #3?  I thought that I would need to have a trigger: HasItem, to check if an NPC actually has something before using GiveItem.  I thought it might cause issues if I didn't.  Are you saying that using GiveItem by itself is fine, even if the NPC doesn't have the item in it's inventory to give?  Hell, I figured it might crash the game if it tried to give an item it didn't have.

    For #2 - based on your feedback, that's the one I think I will rely on the most then, unless I want the NPC to be able to use the item in combat AND give it as a quest reward, which is why I did Vaelasa the way I did.  I had a feeling I would need a COPY_TRANS in there, but wasn't sure, and not sure where.  I really appreciate you taking your time to explain all this to me.

     

  5. Heya folks, as I am working on the rewrite for my mod, I've had to change the way I did items as quest rewards for the new way I am importing SoD items to work properly.  They are working as I intended them to, but I haven't done much with dialogues, so I would appreciate some feedback on how I did these to see if I made any glaring mistakes that might cause issues.  In case it matters: I had my registered prefix changed to "K0" from "DTK".  Having that one extra character to work with really helps more than I thought it would.

    Example 1

    EXTEND_BOTTOM VAELASA 4
    
      IF ~HasItem("bdbrd01",Myself)~ THEN DO ~AddexperienceParty(32500)
    TakePartyItem("misc4n")
    GiveItem("bdbrd01",LastTalkedToBy)
    SetGlobal("SummonDryads","AR1200",1)
    ~ EXIT
    END

    Example 2

    EXTEND_BOTTOM UDSOLA01 161
    
    IF ~Global("BD_HAVE_SOD","GLOBAL",1)
        Global("K0_SOD_IMPORT_75","GLOBAL",1)~ THEN GOTO K0SODIMP
    END
    
    APPEND UDSOLA01
    
    IF ~~ THEN BEGIN K0SODIMP
        SAY @80003
    
    IF ~~ THEN DO ~GiveItemCreate("bdbrd02",LastTalkedToBy,1,0,0)
    SetGlobal ("K0_SOD_IMPORT_75","GLOBAL",2)
    EscapeAreaObject("Tran2100")
    ~ EXIT
    END
    END

     

  6. 25 minutes ago, J Beau said:

    FYI - 4-23-2024 is the standard dating format in the United States. You will occasionally see other formats but my drivers license, for example, uses this format. Daeros is legit in his usage.

    I'm really looking forward to the mod. If I could add a small suggestion. Would it be possible for you to separate the item upgrades into "quality of life" vs weapons. For example in Weimer's old item upgrade mod, combining rings of protection with regeneration was great because you didn't have to keep switching out items. But you also had these really OP weapons that were just too tempting to not use. Or maybe make it easy for the end user to cut out some items before install.

    The upgrades in general are going to get a re-think (I think about them quite a bit during the 'boring' parts of the re-write).  You are correct in that I ended up with WAY too many OP items, even though that wasn't my goal.  Sometimes when creating something new, I get a little too excited about what I can make it 'do', and end up going overboard unintentionally.   I hear you on the QoL stuff, though my approach to it may be a little different than what you are thinking.

    For me, QoL would be things like the keyring, new ammunition types, combining bard instruments to save on quickslots, things of that nature.  Using the example you gave, combining rings of protection with rings of regeneration:  Yes, it does save slots and swapping items out, *BUT* it can also result in the same overpowered items you mentioned.   Can you give me some ideas of what items you had in mind of combining?

  7. 12 hours ago, Jarno Mikkola said:

    How does this work:

    To put months before the day, and then the year ? Makes no sense. It's either dd-mm-yyyy, or the reverse; yyyy-mm-dd. Aka, what's the most important number, yours seems to be the Month.

    Of all the things to complain about.....  At least tell me that that mod sucks and I smell like boo-boo or some such, if you're going to complain :)

    Just for you, going forward I'll do timestamps as: yyy(because no one here is going to see that forth digit roll over again anyway) hh:mm (because lets be accurate) and ww (because which week of the year is important!)

  8. I've completed the first component of the re-write, which is allowing the import of additional SoD items using the same/similar method that BD used for the original SoD importables.  I've tested everything on clean installs of BG2 to verify functionality, at least at a base level. 

    I can already say that importing saved games from a heavily modded version of BGee/SoD results in many of the importable item flags not being properly set (even the original item flags from BD) even though the items are indeed present in the party's inventory in the imported SoD save.

    This doesn't seem to happen if I import a save from an un-modded (other than modmerge) SoD game save.  I can't really see why this is the case, since it's only checking for SoD item filenames that are present in the vanilla game, but I digress, more testing is needed.

    On that note, I have included a beta of the new build for those who would like to try it out, and provide feedback on their experience.  In the TP2, there is a commented-out line that will run a script to force all of the Global flags for SoD importables (new and old) 'ON'.  Just delete the '//' in front of the line and save the file if you'd like to test in that manner.

    When providing feedback, please make sure to mention if you import your saved SoD game from a modded, or unmodded BGEE/SoD install.

    Lastly - you *must* start a new game in BG2 and import an SoD saved game for this mod component to work properly.  It will not work with a save from the BGEE portion of the game, EVEN IF you have the SoD items in your inventory.  This is true even for the original importable SoD items from Beamdog.

    For those who aren't familiar and are wondering why this is:  Because there is a script that runs ONLY when you start a new BG2 game which does several things.  One is to check for a SoD game (if you import) save, and set a flag for that.  Another is to scan the inventory of the party from the imported save to see if it contains items that are importable, then sets flags for each of them before removing everything from the save's inventory.  BOTH of those Global variables have to be 'ON' for each and every importable SoD item, old and new, for them to show up in their assigned spots in the game.

    For those who dont trust this method (I'm one of you), there will be an additional component, just like before, to force the importable item flags to be 'ON'

    Could I just shit-can this method and place everything manually, instead of relying on scripts?  Yep, pretty much did that before, but I got a lot of feedback asking for a more natural experience.  Am I going to have this as an option?  Yes and No, see above.

     

    P.S. - I figured it out.  Only items that are in the protagonist's inventory, are not a container (the keyring), and not *inside* a container (bag of holding), will be counted and the proper import flag set.  Which, in hindsight, makes sense, as the protagonist is the only character that actually gets "imported" from the save.  I would assume that if you were to import a multiplayer SoD save, or a SoD save with more player-generated characters, their inventories may be counted as well, but I haven't tested that.

    So what does this mean for the mod?  It means that at maximum, only 36 items can be imported using a method that scans the PC's inventory when starting a new BG2 game.  At least, as far as I can tell.  Which, if I am being honest, really isn't a bad thing at all.  It actually helps in preventing over-itemization.

    It is making me rethink a few things regarding the SoD importables.  I believe what I will do is have a handful of SoD items be placed into BG2,  regardless of whether you had them or not in your SoD save.  Currently that list consists of:

    1.  The Key Ring.  Its a quality of life item that's too good to leave out, and doesn't import using the method I implemented since it's a container.

    2. The new ammo types in SoD - I already had just placed these on vendors, etc... since they are consumables.

    3. The new bard instruments - these are kind of consumable, and only bards are going to be able to have them in their quickslots, so unless your PC is a bard, you probably aren't going to want to waste any "import slots" on these.

    4. Flavorful, fun items, like the changeling vest, or clerics vestments.

    Given those examples, I am open to suggestions from you all on items from SoD you would like to see placed into BG2, that doesn't require you to have them on your person from an imported save. 

     

     

    DTK_ISKPack-Beta.zip

  9. I've been able to put a good bit of work into the changes/rework of this mod since the last update, and while I haven't been able to make as much progress as I would like (which pretty much never happens :) ),  I've gotten a good portion of the first component, importing more SoD items in a similar manner as how Beamdog did, completed.

    I'm at the point where I am placing the items, and it's been a slog.  It's much more scripting, and far less of just being able to "copy_existing" and add the item.  Annnnnnnd, I keep running into snags during testing that have to be corrected as I go.  One lesson I had to re-learn, the hard way, is that when adding items to containers/creatures using scripts, you really have to pay attention to the actual string-name as opposed to just the filename.  They don't always match, and you gotta go by the string-name when doing this stuff via in-game scripts.

    For example:  I just spent the last hour trying to figure out why in the hell the cloak of minor arcana was not showing up on Mekrath's corpse.  I checked all my syntax and didn't see anything wrong.  tried over, and over.  At first, I thought it was just me killing mekrath so fast that the script didn't complete in time.  This is something that can happen when you are teleporting around using cheats and godbows.  If you want proof of this - try doing it with Tazok.  If you teleport into Firkraags lair, then pop back out and kill him real quick, the Dragon Blade +3 will not be on him, even if all the correct flags for the import are set.  That said, these are extreme examples and should never show up during real gameplay.

    Back to Mekrath and the Cloak:  After getting myself frustrated to no end, I looked over his .cre file in NI, then looked at the name one last time, and thought "wait a minute... does the same shit that applies to container names in scripts apply to creatures?".  Sure enough, it does... ugh.  Lesson learned....again

    P.S. - Or at least it *CAN*.  Good grief sometimes it just comes down to trial and error.

  10. About a year and a half ago, I made the switch from Windows to Linux.  I went from never having used Linux before, to running Arch with the KDE desktop.  It honestly hasn't been all that tough, and I've found it fun, I like figuring things out.

    I've been using Kate for editing my mod, which is included with KDE, and it seems to work fine for the most part, but every once in awhile, I will get a syntax error that leaves me scratching my head.  Reminds me of when I first started out modding using notepad in windows, before I was kindly turned onto notepad++, and to make sure I was using UTF-8 encoding, so I checked my settings and made sure Kate was set for that.

    Anyone have recommendations?

  11. 1 hour ago, morpheus562 said:

    When I made Forgotten Armament a year or so ago, your mod was not one I used but one I ensured compatibility with.

    Here are the locations for all net new items I add: https://github.com/Gibberlings3/Forgotten-Armament/blob/main/ITEM-LOCATIONS.md

    This lists the items coming from IWD and the .cre/.sto files they are attached to: https://github.com/Gibberlings3/Forgotten-Armament/blob/main/forgotten-armament/components/add_items_iwd.tpa

    This lists the items coming from NWN2 and the .cre/.sto files they are attached to: https://github.com/Gibberlings3/Forgotten-Armament/blob/main/forgotten-armament/components/add_items_nwn.tpa

    Thank you for this, I understand what you mean now.  And yes, I do my best to take other items from mods into account (the ones I'm familiar with, anyway), when it comes to placement.

    I wasn't planning on changing placement much for the imported stuff, so if you've already accounted for them in Forgotten Armament, we shouldn't have too many issues.  I'll add your mod to my list of mods I use for playtesting.

  12. 13 hours ago, morpheus562 said:

    With the updates to the new item adds and SoD imports, are you going to be doing any checks to ensure compatibility with other mods that do the same?

    New items, spells, etc... will have my registered prefix in the filenames, so unless someone else is using it in their mods, that will cover those.  For SoD and other pre-existing items, each %filename%.itm is checked to see if it already exists before installing.  Outside of that, I dont know each and every mod by heart, so I'll have to depend on my own playtesting and community feedback to sort out incompatibilities.  I can't account for every single mod out there, but the most popular ones, like tweaks, shouldn't be a problem.

     

    That's why I am planning to post up the .tp2 from time to time, if another modder such as yourself sees something I could do better to make it more compatible, I would be grateful for the feedback on it.

  13. As I've been going through the mod to rework the things I wanted, I quickly realized just how much of a mess the mod is in it's current state ( at least in terms of how I have structured it, the installation, etc..) and how difficult it would be to rework it without going back to the drawing board.....

    So, after hemming and hawing over it for a day or so, that's exactly what I have done.  I'm more or less starting over from scratch.  I want to make this thing as clean and modular as I am able so that in the future, I wont have to do this AGAIN. ><

    #1 - I've decided that I will be changing the name of this mod to better reflect what it has in it.  It will simply be named:  "Daeros Trollkiller's Item-Spell-Kit Pack.  No muss, no fuss.  Tentative for now, but after all the complaints I got on the current name not being "accurate as to what the mod does", I figure this will make things quite clear.

    #2 - Each and every major component of this mod will be optional.  Just want some more SoD items imported into BG2 and nothing else?  You got it.  How about just some new spells without any other fluff?  You bet.   What about just one of the class kits I plan to add?  That too.  The only planned exceptions to this rule will be the "item upgrade" type of components that rely on one of the others to be installed first, for instance:  SoD item upgrade component will require that you install the additional SoD item component.  (otherwise there would be nothing to upgrade, and therefore, pointless to install)

    #3 - The item upgrades and new spells are going to be overhauled a good bit.  Also plan to add some altogether new items of my own creation.  Don't expect much of the old upgrades, spells, or their recipes to stay the same.  Some certainly will, however.  I'm doing this in response to feedback I've received, as well as changes I simply want to make.  My overall goal with these remains them same: keep it interesting, useful, and not overpowered.  I've brainstormed quite the list already for this part.

    #4 - The aforementioned class kits: I've already created one of these awhile back for the Ranger that I plan to add, and have some ideas for a few others IF I can make them work the way I want them to.

     

     Progress thus far:

    First component I've been working on is a simple addition of more SoD items to BG2 (and later, perhaps adding some to IWD as well).  Made good headway on it so far, some of the items previously imported have been stripped, but not a lot.  Another new thing I will be doing here:  I plan to bring these into BG2 in the same manner Beamdog did for the SoD items they already import.  This way, it can feel more "natural" for folks who want to be able to import their save from SoD into BG2 and only have the SoD items that they actually had on them imported into BG2.  For folks like myself, who don't like relying on that mechanic, there will be an optional component to force the import of the new SoD items, along with the old SoD items, in a similar manner as I had before, wherein there will be sub-component options to choose between the mutually exclusive items, such as the Dragonscale Armor or the Dragonscale Shield +3, since you can only get one or the other in a single playthrough of SoD.

     

    Phew... that was a lot to say, but this is going to be a lot of work.

    P.S. - forgot to add:  If I can remember, I might post of the .tp2 of the mod from time to time as a means of allowing modders with more skill than I to chime in on ways I could write it, or parts of it, better.  I still consider myself to be very much on the novice level compared to others here on G3.

  14. First and foremost - my apologies for the lack of updates and responses here.  The last year has been very difficult for me and my family with losses, and I simply haven't had the time or desire to work on the mod or even play the games.

    I've  finally gotten the urge to play again, and am currently doing a playthrough of BGEE+SoD, with this mod installed to see what is and isn't currently working.  So far, finding much more broken than I thought I would, TBH.  But it's a good thing, since I can't fix what I dont know is borked.

    Going forward for the next update, I am going to keep things simple so I don't get overwhelmed, and I am rusty as hell, so I'm sure I will have to re-learn, and learn some new modding methods to get things working the way I want.  So here's the short list of my plans for 2.0.7:

     

    1. Find and fix bugs -#1 priority.

    2. Re-write the new spells as their own, separate component.  Will check into using a spell tool as to not use limited slots afterwards.

    3. Review of content - Change some things, remove some things, add some things, etc...  Nothing is off the table.  This part is always my favorite to work on.

    4. Renaming of this mod - This mod has grown far beyond the original scope, and needs a rename to better fit.  Something more simple, such as "Daeros' Item and Spell pack".  Open to suggestions.

×
×
  • Create New...