Jump to content

Feedback: IR v4 Beta


Mike1072

Recommended Posts

I noticed that all throwing returning weapons must be switched from melee to range via item use instead of having 2 modes like others, is there a reason for that other than legacy ?

Well one sort can be used as a melee only, and thus also in the second hand and so dual wield, while the other(ranged) can be only used in the main hand, with or without a shield.

Link to post

Right, I thought this got changed by 2.0 but looks like no.

 

This being said, I feel like it would be better for the user to have a main mode with throwing and melee capability and then a second mode being "dual wield". It is possible to have a throwing weapon in main hand and a melee weapon in offhand. Switching by right clicking on the weapon doesn't cause any issue.

Link to post

This being said, I feel like it would be better for the user to have a main mode with throwing and melee capability and then a second mode being "dual wield". It is possible to have a throwing weapon in main hand and a melee weapon in offhand.

Not at least in the non-EE BG2. Yes, the ranged version can be used in melee too via right clicking, but it's not the same as the ranged, as you have to transform it using the ability to use it in the second hand, so it being the ranged variant then, you are not able to place it or another weapon to the offhand slot at all with it equipped, or equip it if you already have an offhanded weapon equipped.

Edited by Jarno Mikkola
Link to post

I'm going to suggest prompting the user with a quick READLN for the stack values. I personally like very different values for different type of things (80 for ammo, from 20 to 40 for daggers/axes, 12 for potions and 999 for gems because why not).

Link to post

I'm going to suggest prompting the user with a quick READLN for the stack values. I personally like very different values for different type of things (80 for ammo, from 20 to 40 for daggers/axes, 12 for potions and 999 for gems because why not).

 

READLNs are a pain to support in BWS. If you must have one, please use subcomponents, so there are a few standard amounts as other subcomponents and then a "custom amount" subcomponent where it does a READLN and asks for a number.

 

Choose a maximum stack size for potions:

1] 12

2] 20

3] Custom (prompt for a number)

 

Etc.

 

Also as noted, various other mods already tweak this (Tweaks Anthology and the Difficulty and Tweak mod are prime suspects), so I'd question the necessity of tweaking it at all here also...

 

Edit: Another argument for minimizing READLN use -- what the user entered doesn't show up in the WeiDU.log, which means you have to ask for additional info when supporting users of the mod.

Edited by agb1
Link to post

 

I'm going to suggest prompting the user with a quick READLN for the stack values. I personally like very different values for different type of things (80 for ammo, from 20 to 40 for daggers/axes, 12 for potions and 999 for gems because why not).

READLNs are a pain to support in BWS. If you must have one, please use subcomponents, so there are a few standard amounts as other subcomponents and then a "custom amount" subcomponent where it does a READLN and asks for a number.

 

Choose a maximum stack size for potions:

1] 12

2] 20

3] Custom (prompt for a number)

 

Etc.

 

Also as noted, various other mods already tweak this (Tweaks Anthology and the Difficulty and Tweak mod are prime suspects), so I'd question the necessity of tweaking it at all here also...

 

Edit: Another argument for minimizing READLN use -- what the user entered doesn't show up in the WeiDU.log, which means you have to ask for additional info when supporting users of the mod.

 

Yeah, sounds like two good reasons not to use READLN (at least by default).
Link to post

Edit: Another argument for minimizing READLN use -- what the user entered doesn't show up in the WeiDU.log, which means you have to ask for additional info when supporting users of the mod.

Heh, just ...

ACTION_READLN ~variable~ 
OUTER_WHILE !(IS_AN_INT %variable%) BEGIN // or any other condition you want.
  PRINT ~error message~
  ACTION_READLN ~variable~
END
PRINT ~variable~
..and it will, definitely.

 

I personally use unlimited for all, I hate micromanaging my inventory and if someone can carry a dozen armors, 999 arrows won't make a difference....

..999 is not the max you can set the stack limit... it's 32 000+ few. So don't you go and set it to 999 either. Edited by Jarno Mikkola
Link to post
Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...