Search the Community
Showing results for tags 'tutorial'.
Found 28 results
I have a bunch of macro, written for myself, maybe they might be useful for others. Actually, I'm quite surprised why isn't there a community resourse that would hold a variety of them yet. Macro names are intuitive, required and optional variables are listed in relevant .txt files. Obviously, I don't guarantee anything, anyone can use them in any way and form. Basically, all that needed to use them is to put a line in .tp2, like "INCLUDE ~mymod/lib/g_itm.lib~", and they will be available. They work, but they ARE NOT heavily tested, particularly g_eff.lib (unlikely I will heavily test them myself ever), so use them on your own risk. Tell me if you find a bug, please. Hopefully they will save some time to somebody, at least. edit: the link contains the updates ones, with readme formatting like in weidu readme archive with libs(9 kb) There are 3 libs, see more detailed descriptions in .txt files in the archive: g_itm.lib - item management. Macro: DELETE_CRE_ITEM DELETE_STORE_ITEM DELETE_AREA_ITEM REPLACE_CRE_ITEM REPLACE_STORE_ITEM REPLACE_AREA_ITEM ADD_AREA_ITEM ADD_CRE_ITEM_FLAGS REMOVE_CRE_ITEM_FLAGS g_eff.lib - effect management DEL_SPL_EFF DEL_ITM_EFF DEL_ITM_EQEFF DEL_CRE_EFF DEL_SPL_EFF_ALL DEL_ITM_EFF_ALL ITEM_EFF_TO_SPL ADD_SPL_EFF ADD_ITM_EFF ADD_ITM_EQEFF ADD_CRE_EFF g_cre.lib - only 2 macro so far READ_SOUNDSET WRITE_SOUNDSET
The GROUP flag came about in discussing component management with an abnormally large number of independent components, e.g. BG2 Tweaks, and was added as a feature in WeiDU v192. Previously WeiDU lacked a satisfactory way to organize such a modâ€"the closest feature would be the top level ASK_EVERY_COMPONENT, which only allows for a single all-or-none approach. The solution is a new component flag, GROUP, with the following syntax (and example): GROUP string BEGIN ~100% Learn Spells~ GROUP ~Convenience Tweaks~ // component code BEGIN ~Identify All Items~ GROUP ~Convenience Tweaks~ // component code BEGIN ~Give Edwin his BG2 Stats~ GROUP ~NPC Tweaks~ // component code BEGIN ~ Give Jaheira her BG2 Stats~ GROUP ~NPC Tweaks~ // component code Upon installing the mod, the player is now presented with meta-options on each group at a high level: Would you like to display the category [Convenience Tweaks]? [Y]es/[N]o Would you like to display the category [NPC Tweaks]? [Y]es/[N]o Selecting [N]o on any group suppresses those options from being displayed, leading to a simpler and more controlled installer experience for the player. In the provided example, selecting [N]o to Convenience Tweaks and [Y]es to NPC Tweaks would result in WeiDU starting installation by asking to install the Give Edwin his BG2 Stats component. GROUP operates independently of SUBCOMPONENT, meaning you can use both to organize the mod as needed. A few other items of note: A component can belong to multiple GROUPs; a component is not offered for install if and only if none of its member groups are selected You could, in theory, have two components in the same SUBCOMPONENT grouping but different GROUPs. Don't do this. If some components of a mod are in a GROUP, but others are not, the non-GROUPed components will always be presented. Using a GROUP anywhere in your mod will act as an implied ASK_EVERY_COMPONENT tp2 flag.
The issue here, budding modders and modstresses out there, is that if you use any sort of WEIGHTing for creating new entries in Biobanter DLGs, you have to be sure that you weight beneath all of the states in that DLG which are called by script: such as LOVETALKs, somebody died/somebody was raised talks, etc. Those values are reasonably easy to find using InfExp/NI/DLTCEP's editor (actually, NI's Edit mode in the state trigger list is probably the best way to locate it quickly.) You can also glance at the Banter Packs for "safe" zones for weighting.