Jump to content

igi

Gibberlings
  • Posts

    1,222
  • Joined

Posts posted by igi

  1. There was a handy discussion in the Aran Whitehand forum which made some suggestions for area types (rather than "this area was added by mod x") - 

    I believe the summary was:

    256	SHOP		   Can buy/sell items
    512	TEMPLE		 Can purchase healing spells
    1024   TAVERN		 Can purchase drinks (rumours)
    2048   INN			Can rent a bed
    4096   STRONGHOLD	 Player stronghold
    8192   EXTRAPLANAR	Outside the prime material plane
    16384  -			  Unused
    32768  -			  Unused

     

  2. There are 4 BAM files that ship with the game, tvrnqul0 through tvrnqul3. The 2 tavern quality bits indicate which of these 4 BAM images are displayed on the drinks section of the store. I believe all stores in BG1 have neither flag set, and so show image 0 (a pint mug). The image below has both flags set, and shows image 3.

     

    image.png.3239d24777601e21fbfa491d04813878.png

  3. This idea would allow for the current standard format in simple descriptions and layout to remain as well as providing a central locale for additional information whether it be links to weidu code that will make editing certain file types easier or further descriptions to help readers better understand the varied usages of certain IDS values.

     

    I like this idea, and it's why I have resisted putting some information into the IESDP - it doesn't belong there. A linked resource containing such info would be useful, as long as there is clear separation of what goes where.

  4. My only other concerns with a wiki would be:

    a) The IESDP may lose focus. As it is is is a reference for modders which (hopefully) has some central structure to it. If it were a wiki I feel it would rapidly expand to cover extreme edge cases in depth, becoming less useful to a more general audience. I would argue that e.g. a four paragraph description on the True() trigger is probably more than most people are looking for.

     

    b) Inconsistency. The IESDP is currently internally consistent in its IE language (feature block, extended header etc.) and technical language (we always start counting from bit 0 etc.). Also, I'd have to ritually murder a kitten every day if the grammar reverted to anywhere near its previous standard.

     

     

     

    While I enjoy maintaining the IESDP, it's also quite soul destroying to see the contant criticism and sniping - if it does become a wiki I may take the oppotunity to relinquish my duties completely.

  5. It has been considered. It's not happend yet due to the following factors:

    a) No-one has sufficient inclination to find time to do it

    b) The majority of the IESDP is table based, which is probably the hardest thing to do in a wiki

    c) There are likely to be issues related to the downloadable copy of the IESDP

    d) I'm unsure whether the group of people trust-worthy enough to have write access would make it a wortwhile investment of time

    e) The current forum structure serves a role as a storing house while information is verified

     

    Other than that, it's a good idea.

  6. Research topics:

     

    If you have some free time, and want to be world famous forever (well, you'll have your name in the IESDP credits list), have a look at this post, which contains a partial list of unknowns, and maybe investigate something...

     

     

    ToB opcodes

    0x005: param1 (0,*), param2 (0-5,1000-1005), dices, timing (1), 0xCC (!0)

    0x012: param1, param2 (0-5), dices, timing (1,*), 0xCC (!0)

    0x027: timing (1,*), 0xCC (!0), duration // 0xCC checked if timing != 1

    0x035: param1, param2 (2), timing (1,*), 0xCC (!0), param3 (if 0xCC == 0, else overriden)

    0x043: param2 (0,1,3,4,5,*), resource, duration, param5, timing (1)

    0x047: param1 (lb), param2 (0,1), timing (1), 0xCC (0)

    0x081: param1 (lb), param2 (lw), 0xCC (!0)

    0x087: param2 (0,*), resource, 0xCC (0,*), param3, param1 (lw) (p1 + p3 overridden in some paths)

    0x091: param2 (0-2), 0xCC (!0)

    0x0B1: param1 (0,*), param2 (2-8), resource, duration (copied), timing (copied), 0xCC (copied), param3 (0,*) (bool)

    0x0E8: resource, param5, 0x78, param2 (0-11), param1 (0-3), param3 (!0), parent resource (if res_type == 1)

    0x0EA: param1 (lb:0-9), param2 (lb:0-3|uw), parent resource (if res_type == 1)

    0x0EC: param2 (1-3), duration, 0xCC (!0), timing (copied)

    0x100: resource, param5, 0x78, param3 (!0), parent resouce (if res_type == 1)

    0x10D: param1 (lb), param2 (1,*) (1 uses p1 + negated p1), duration

    0x126: param1

     

    CRE Format

    0x002a

    0x0076

    0x0084

     

    STO

    0x0010 - bits 7,8, 11

    0x0024

  7. The Infinity Engine Structures Description Project (IESDP) is an effort to document the Infinity Engine. The IESDP contains information on file formats, opcodes, scripting and more. It is the central point for technical information relevant to modding the Infinity Engine. The IESDP is currently maintained by igi, though there have been several custodians in the past, and even more contributors.

     

    The IESDP is hosted by The Gibberlings Three, and can be found at:

    https://gibberlings3.github.io/iesdp/

     

    There is also an IESDP update forum, where you can post contributions, questions, updates, queries and postulations:

    https://www.gibberlings3.net/forums/forum/54-iesdp-updates-and-info/

     

    If you want to contribute to the IESDP, check:

    - this forum for posts with info that hasn't been included yet (once done, threads get moved to the archive)

    - the issue queue: https://github.com/gibberlings3/iesdp/issues

    - this post for a selected list of research topics: https://www.gibberlings3.net/forums/topic/1696-research-topics/

     

    If you have archives of any posts or information from the TeamBG IESDP update forum, which had *not* been moved to the IESDP archive forum, please post them on this forum. A summary of those missing topics is located here:

    https://www.gibberlings3.net/forums/topic/1689-missing-threads-from-the-tbg-forum/

     

    /igi

  8. Lo folks,

     

    IESDP stands for Infinity Engine Structure Description Project. It's a site dedicated to explaining the Infinity Engine from a modders/developers point of view. The IESDP has been around in various incarnations for several years, and has lots of information on almost everything, from scripting triggers/actions to file formats, to area filename lists, and more besides.

     

    Go and look at it (http://iesdp.teambg.net/).

     

    If you have any comments, spot any errors, want to contribute, or complain, pop over to the IESDP update forum: http://www.teambg.net/forum/?board=28

     

    /igi (current maintainer)

×
×
  • Create New...