AL|EN

debug https://paste.ee/r/iIizv

/////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\ /////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\ ///// \\\\\ ///// Bonus Merchants \\\\\ ///// \\\\\ /////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\ /////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\/////\\\\\ BEGIN @117000 DESIGNATED 1170 GROUP @13 REQUIRE_PREDICATE GAME_IS ~soa tob bgt~ @25 Redme says: so REQUIRE_PREDICATE GAME_IS ~bg2ee eet soa tob bgt~ @25 EDIT: and in case you missed: According to the following thread, the ToB style Leveling may be obsolete for EE 2.0 and higher: https://forums.beamdog.com/discussion/49007/level-1-npc

I'm too tired today, will update BWS this week.

another error using BGT: weidu log

The reason to prefer new mods ( not every mod but Tweaks from Cam deserves to be preferred without a blink of an eye) instead of old mods which was coded years ago is to encourage new moders to find better ways to achieve something (EET_Tweaks XP adjustment!) and actually for testing purposes - without selecting new mods as default, nobody would actually test anything. Now we identified a bug and the solution will come soon - I prefer this way instead of suddenly discover such bug after half year. Feedback is welcome and I'm open to suggestion about this matter.

This link: http://lynxlynx.info/ie/modhub.php?subtledoctor/Refinements_EE&pre will always lead to the most recent version.

No, I've decided that--going forward at least--I'm going to extend my modding prefix to my mod folders as well. After all if we're worried about name space collisions in the game, it's possible (though unlikely) we could have them outside as well. Got it but still, you should call it "cb_TTA" or "cb_TheTweaksAnthology" if you wanted to add you modding prefix. Don't repeat old mistakes like for eg Fishing for Trouble and "dq" mod folder...

While I might suspect why mod folder is called "cd_tweaks" but I think it's better when mod folder reflect actual mod name like "TTA" or "TheTweaksAnthology". Wana test github pull request feature?

New version install without problems

Ok, thanks, I will use you code. The bug report only appears with the combination of the mods from weidu - do you need a changelog from specific file maybe?

Also I was under impression that "Component 2000: NPC kit choices" / "Component 3000: multiclass kit choices" are also applied to PC and dual-classed warriors clerics - could you please add such option?

I've selected "Choose an class for Brawnen: 0242 Make Brawnen a multi-class fighter/cleric

Hi, new bug 2.1 weidu log:

Yet another limitation to be removed

Thank you!

Debug:

Just for the record (I think it's not the reason): User Ignored Rule: C:bg1ub(16):BGTTweak(600) @16=Creature Corrections @600=Druid/Ranger-responsive bears in BG1

Another bug/question: Does the Workroom Common Area sub-forum is excluded from "View new content" I've missed whole "Hosting G3 Mods on GitHub" discussion...

Hi, I cannot find "Site/Forum Feedback" thread so I will use this topic: there is an bug with "Load more topics". How to reproduce: 1. Go to the Workroom Common Area subforum 2. Click at "Load more topics" Notice that "supposed new threads" are exactly the same from the first page.

I'm using this v4 BETA link which you gave me long time ago: https://www.dropbox.com/s/rnw1s9dzxr0oy9v/... and when I open lib\descriptions.tpa file, there is no function update_item_descriptions_to_bgee I've put this code: http://gibberlings3.net/forums/index.php?showtopic=26082&p=223749 to lib\descriptions.tpa and I was able to install it just fine.

Anyone know how to fix this error? The only mod installed before IR is Spell Revisions.

Thanks!

I would be grateful for not forcing players to install any software to be able to use this mod. Use zip, it can be opened by every OS without custom apps.

Stop posting anything until you update you game to 1.3. Indeed, changing version of BG:EE solved my problem! But why such the discrimination?? So now I have 1,3v can I start post anything again ? I'm glad that upgrading fixed you problem. It was my first suspicion. The "discrimination" as you called it, was for saving precious time for the people which wan to help you debbug you problem without knowing that you using old game version. Fot the techy-stuff, no compromise. GemRB is not 100% compatible replacement of the IE engine. I also cannot be used for EE games. You might like open source idea but it isn't an some kind of magic spell that makes everything better than closed-source projects. As for the patch: the fact that old version works for you it doesn't mean that it works fine. You don't want to wonder "maybe this new path fix some game-breaking bug which i might face" so you just install it. It' is nothing fanatic about trying to use new version of the game/software.

Stop posting anything until you update you game to 1.3.