Jump to content


ark7

Member Since 24 Jan 2008
Offline Last Active Dec 26 2013 06:20 PM

Topics I've Started

A little screw up...

26 December 2013 - 11:34 AM

Ok, this is not *technically* a bug, but I think I've screwed up the romance with Arath either by romancing Branwen, or doing one of the encounters from the Romantic Encounters mod. Since I found no crossmod notes regarding Arath, I thought I'd be fine =/ (and it made sense with the little fanfiction plot that was going on in my head). Either this, or maybe I really screwed up when I told him I'm not a boy looking for a quick fix (contradictory, eh?)

 

Anyway, I've tried resetting LK#ARATHROMANCEACTIVE back to 2, and then I had the nightmare talk, but after that the variable keeps resetting back to 3. I've tried changing variables from Romantic Encounters and Branwen to 0, but no matter what I do the Arath variable keeps going back to 3. As far as I understand, 3 means romance over, amirite?

 

I've already invested far too many hours into this play-through, so I'd like to know what variables might be interfering and causing LK#ARATHROMANCEACTIVE to always reset to 3. Or, in case I really did say something I shouldn't, what variables I should set to what numbers in order to go back a couple of lovetalks.

 

Other variables that might be relevant to this case:

LK#ARATHLOVETALKS 13

LK#ARATHBHAALSPAWN 9

LK#ARATHINNSEX 2

LK#ARATHBREAK 2

LK#ARATH_GIRL2 1 (???)

LK#ARATHKEEP 3

LK#ARATHSHADE 3

 

Thanks in advance :)


Script suggestions

07 December 2013 - 07:03 AM

First of all, I'd like to thank the creators of BP Series for the awesome scripts! I've been using them for a brief time, but they've helped a lot already  :)

 

However, there's one thing that's been annoying me: I like to scout ahead with my ranger or thief, but if I see an enemy, the rest of the party comes crashing in from half the map away, even if the enemy hasn't attacked me at all (because I'm stealthed). I've had party members walking into traps and drawing undesired aggro because of this.

 

So I'd suggest implementing a "detection range" for all scrips, preventing the character from attacking targets outside his detection radius unless ordered to. I don't know if this is actually possible, but it would help immensely, especially if one could toggle it ON/OFF. Or maybe toggle for different ranges, such as "close" (~2/3 screen-range), "medium" (~5/3 screen-range) and "unlimited".

 

I've also noticed that some scripts (namely the casters) tend to spend precious resources unnecessarily in easy battles, so I'd like to suggest a generic semi-passive script that automatizes battle modes and basic skill use for all multiclass combinations, but leaves spell-use and advanced item use in the player's hands.

 

Something like this:

- Automatic: Attacks enemies in detection range with whatever weapon is equipped (never switches weapons unless commanded)

- Automatically casts long-duration buffs (8h or more) on self, trying to keep them always active

- Toggle: Melee adaptation (automatically switches to a melee weapon if attacked in melee)

- Toggle: Keep distance (tries to move away if attacked in melee and switches to a ranged weapon when no enemies are adjacent)

- Toggle: Enemy detection range (close, medium or unlimited)

- Toggle: Use healing potions and antidotes/elixirs (but not other items or potions)

- Toggle: Stealth mode

- Toggle: Find traps mode

- Toggle: Bard song mode

- Toggle: Party healer mode

- Toggle: Turn/Rebuke undead mode

- Hotkey: Casts self-buffs (all classes supported)

- Hotkey: Casts party-buffs (all classes supported)

 

About the party-buffs hotkey, I'd suggest single-target buffs to be used if enough slots are memorized to buff the whole party. In this case, the character would cast the multi-target buffs then go about using single-target buffs on each party member in turn.

 

In the old BG2, there was a script that did something like this, but it forced buffs to be cast instantly, to save their duration (and the player's time). I like this idea very much, but some people could find it cheesy, so I'd suggest implementing two versions if you guys decide to make use of this script idea =P