Jump to content


argent77

Member Since 24 May 2010
Offline Last Active Today, 03:25 AM

Posts I've Made

In Topic: Question to Changing Item Usability via WRITE_BYTE

08 June 2018 - 06:20 AM

Well, unfixpacked BG2 would allow half-orcs to wear the item. So I guess it was only added as a precaution.
 


In Topic: Question to Changing Item Usability via WRITE_BYTE

08 June 2018 - 04:47 AM

That two initial read operations are not strictly needed, because WeiDU automatically reads the content into the variable THIS for each write operation.

The logic of the write operations looks correct though. With the hint from above and the use of some helpful WeiDU constants it would result in:

COPY_EXISTING ~misc5x.itm~ ~override~
  WRITE_BYTE 0x1e ((THIS BOR BIT3) BAND BNOT BIT2)
  WRITE_BYTE 0x21 (THIS BOR BIT7)
 BUT_ONLY

Or combined into a single write operation:

COPY_EXISTING ~misc5x.itm~ ~override~
  WRITE_LONG 0x1e ((THIS BOR BIT3 BOR BIT31) BAND BNOT BIT2)
 BUT_ONLY

You can optionally replace BOR by |, BAND by & and BNOT by ` (back quote sign) to reduce code length.

Btw, the code makes "...Neutral" and "Half-Orc" unusable and "Good" usable. And yes, NPC-specific restrictions in EE games are only tied to creature (script) name. Alignment, race, etc. doesn't matter.


In Topic: Multiple charges on an item?

02 June 2018 - 01:16 PM

It should be enough to set the "# charges" to the total number of charges and "When drained" to "Item vanishes" in the ability header.


In Topic: [SOLVED] Is BAM V2 supported by ARE background animations?

01 May 2018 - 08:44 AM

Well, I solved it by coding a WeiDU BAM generator to generate the desired BAM V1 file with alpha palette.

I still hope BAM V2 will be more widely supported in future EE patches. It looks like this format can currently only be used in UI related contexts.
 


In Topic: [SOLVED] Is BAM V2 supported by ARE background animations?

29 April 2018 - 11:54 AM

I changed pretty much every flag, including bit 15. Except when bit 13 (WBM) was enabled the map always crashed. Enabling bit 13 simply ignored the BAM resource. (And bit 14 is still a big mystery.)

BAM V2 is needed because of alpha transparency. Unfortunately there is no BAM editor available yet that supports alpha channel in BAM V1 palettes, NI included.

If nothing else works I can probably use raw pvrz files (each BAM sequence consists of only a single frame). But that would require to create several dozens of files in place of a single BAM with several dozens of sequences. Not something I'd like to use if there is another way.