Jump to content

K4thos

Modders
  • Content Count

    1,371
  • Joined

  • Last visited

1 Follower

About K4thos

Profile Information

  • Gender
    Male

Recent Profile Visitors

13,390 profile views
  1. based on my test with vanilla BG1 link between west edge of Durlag's Tower area and Gullykin (ENTRY_NAME set to N, DEF_ENTRY set to 1) the party ends up in the middle of the northern part of the Gullykin, right here: Not sure what would happen if that part of the map would not be traversable, but in such case you can just use entrance name (btw. BG2 doesn't have a single link that would depend on DEF_ENTRY and in BG1 it's also not that common)
  2. DEF_ENTRY: It's the default entry location (ignored if ENTRY_NAME entrance exists, I think). 1 = Northern edge 2 = Eastern edge 4 = Southern edge 8 = Western edge ENC1-5: ARE file name where optional random encounter takes place (chosen randomly from the available areas). "N" here means "none". ENC_PROB: % chance for random encounter
  3. It's part of the ARE format. The easiest way is to use NI Area Viewer and display all entrances:
  4. everything looks good to me, I really appreciate the work you've done on it. If someone would like to share feedback on those encounters before they are scripted, please share your thoughts.
  5. from weidu documentation: String This is how you tell WeiDU what text you want shown to the player. For international mods or international translations, you may use any encoding you like (that is, you are not restricted to 7-bit characters or Latin-1 or anything like that). is "abcdef" A string can be any sequence of characters not including a " that is enclosed in ""s. or ~abcdef~ A string can be any sequence of characters not including a ~ that is enclosed in ~~s. or %abcdef% A string can be any sequence of characters not including a % that is enclosed in %%s. This is handy for Big5 translations, since " and ~ can be part of Big5-encoded characters. or ~~~~~abcdef~~~~~ That’s five consecutive tildes on each side. A string can be any sequence of characters not including ~~~~~ that is enclosed in ~~~~~s. For example, string #8750 is ~!@#$\%^&*()_+-=[]{}\|;:'",<.>/? and can be given to WeiDU as ~~~~~~!@#$\%^&*()_+-=[]{}\|;:'",<.>/?~~~~~ (the content of the string is shown in red for clarity). or String ^ String String literal concatenation. The second string is appended to the first string. No whitespace is added. Thus "hello" ^ "World" is the same as "helloWorld". you can use REGEXP within REPLACE_TEXTUALLY. Try this to catch both Enemy() and Enemy() enclosed within ActionOverride (that END is not needed): REPLACE_TEXTUALLY ~Enemy()\()?\)~ ~Enemy()\1 ApplySpellRES(somethinghere)~
  6. it was not removed, the code that automatically generates descriptions just wasn't good enough to list it. Since there are no BG items with bonus like this I didn't think about comparing launcher range values. I’ve noticed it listed on the IWD2 side by randomly comparing descriptions in the HTML file. The converted item itself already had correct value (150 instead of 100 - still within visual range, I think), the bonus was just not listed in the automatically generated description.
  7. New versions of HTML files with item descriptions have been uploaded to dropbox. Changelog: - Implemented Saving Throws penalties following feedback from this topic * negated HoF -10 ST bonus * implemented new formula for ST penalties that converts IWD2 inflated values to BG style range of -1 up to -5 - Fixed few Saving Throws assignments: * Xvimian Fang / Xvimian Fang of Despair: Death => Petrification/Polymorph * Lamp Oil: Rod/Stuff/Wand => Breath * Lolth's Sting / Lolth's Cruel Sting: Rod/Stuff/Wand => Spell - Added missing "Weapon range increased by 50%" bonus description (Sophias Flight and Sophia's Arc bows) - Added missing "Immunity to bleeding" bonus description (Periapt of Wound Closure) - Added missing "Damage type: " to Halbards "Slashing or piercing, whichever is better" description
  8. there is no such limitation. All CRE files from vanilla games used in encounters will be copied to unique files. You can design encounters using any CRE files from BG:EE, BG2:EE, IWD:EE, IWD2. Or you can create new CRE files from scratch. yes. It's possible to have random encounter chance, force random encounter, encounter to take place in particular coordinates of the worldmap etc. I can implement it the way a person responsible for designing random encounters envisions it Between IWD1/HoW/IWD2 areas only snow areas since that's what we got and it fits the surroundings. When it comes to random encounter that can happen when you travel between BG <-> Icewind Dale my idea is to give a small chance for an encounter (for example Pirates attack, maybe some monsters like Harpies, Kuo-Toa etc) to happen somewhere on the sea between those locations – that’s why I’ve requested a boat image. You first travel to Icewind Dale via boat (see IWD2 intro for a story framing) and once there you can use worldmap to travel back to BG areas (at least in portions of the story that it makes sense). So even though we're not showing how the travel back and forth looks like the player knows that it's done by the sea each time thanks to the random encounter that may happen. So with this in mind using BG1/BG2 random encounter areas art don't seem like something necessary although I’m not strictly against it if that’s what encounter designer wants to implement. yes. Ideally with percentage chance value for the encounter (for example 5%). For easier implementation additional information where to place the party and CRE files on the map (image coordinates) would be useful too.
  9. whole mod is meant to be installable also on top of IWD:EE down the line, so yes (IWD:EE platform has less priority for now though). Also even though I'm not planning to extract/maintain different parts of the mod as separate mods/components, I'm not against others doing so (if people contributing content for particular feature also don't mind) edit: from the get-go you will be also able to play IWD1/HoW campaigns separately from the BG story via EET "Select Campaign" feature (which works like IWD:EE base game but with additional features that this mod introduces like random encounters, voiced greetings, optional IWD2 rules, etc.)
  10. Thanks for your work, Fluke565. If I remember correctly "deep water" SR color is used in some BG1 maps near water, so can't be replaced without regressions. Yellow color is not used in any BG1 and BG2 areas, which makes potentially fixing it on engine level safe. This could be likely fixed via EEex but on the other hand "sand" sounds are acceptable imo, so not sure if it's worth bothering Bubb with it. currently you're the only person interested in designing actual encounters. If anyone would like to help with it please share your ideas/thoughts in this topic.
  11. here is a dedicated function by Mike1072 for appending to tooltip.2da. If you use it you don't have to worry about missing columns in other rows. tooltip.tpa
  12. I'm afraid I'm out of ideas. Even with the above script Imoen doesn't lose any XP in my game. After loading the save she has: 1 521 077 XP in mage class, which allows her to level up from level 13 to 14, after which she stays at that XP value.
  13. Please upload IMOEN2.BCS file. With it I should be able to at least reproduce that Imeon loosing XP bug (since the EET code for XP decrement is in that file, there has to be something in your version of the script that conflicts with it, even if I can't reproduce it with just SCS component installed).
  14. can't reproduce it with you save after installing SCS component. Jan leveled up to 12/14 (880 000XP * 2 = 1 760 000) which is in line with your CHARNAME total XP in that save = 1 637 498 (not exactly the same value but very close) Imoen also didn't loose the XP like you described. No idea what is happening in your game but it looks like SCS component is compatible with vanilla EET (at least based on this limited test case)
  15. SCS readme file says: so I don't see why Hexxat, Jan or Mazzy getting about 4 000 000 XP when your CHARNAME also has almost 4 000 000 should be considered a bug. Sounds like it works as expected here. The only compatibility issue seems to be Imoen losing her XP like you mentioned. EET adds few lines to her script to handle her XP before dual classing (I think, can't say I fully understand what was the purpose for it), which likely conflicts with SCS code - I will install the component and see what's up.
×
×
  • Create New...