Jump to content

Bubb

Modders
  • Posts

    49
  • Joined

  • Last visited

1 Follower

About Bubb

Profile Information

  • Gender
    Male
  • Mods Worked On
    EEex
    Bubb's Spell Menu

Recent Profile Visitors

354 profile views

Bubb's Achievements

  1. You've already figured things out, but just to document what happens in the hardcoded effect: Opcode #157's visual effect switches to frame 0 of cycle 1 or 2 (randomly picked) when cycle 0 hits its end. The "immobile and scripts stop running" part should happen immediately, even before the animation finishes.
  2. Script actions always get queued up and executed after a complete pass of the script, (after the triggers have been checked), so it's impossible to change how triggers will evaluate during the current pass. The only exception I know of is in IWD2, where the introduction of SCRINST.IDS and DLGINST.IDS allows certain actions to execute during the middle of a pass. So, unfortunately the inverted-trigger mess masterpiece that you've settled on is the only way. Cutscenes are also special in that they have custom script handling. Here's some notable things, not all of them are relevant to your situation, but they might help prevent some confusion in the future: 1) The first action in a block is treated as a placeholder — the engine uses the object it contains to execute all subsequent actions for that block. CutSceneId() is the convention for this first action, but it can be anything. Note that CutSceneId() is basically a renamed NoAction(), its position in the script is the only thing that matters. The first action is otherwise discarded and not run. 2) Continue() is meaningless. Cutscenes process every available script block, even if it already entered one, (unlike object/creature/area/game scripts). 3) There is no event handling, so all triggers with an IDS value less than 0x4000 auto-fail. There's probably more, but that's all I can think of at the moment.
  3. It is indeed an annoyingly unintuitive system. The reason summons can't become familiars is because they are controlled; the engine prevents such creatures from becoming familiars. You need to trick the engine into swapping out their status; I've found this works: IF Global("B3Once","LOCALS",0) THEN RESPONSE #100 SetGlobal("B3Once","LOCALS",1) ChangeEnemyAlly(Myself,NEUTRAL) // I shouldn't be controlled by the player. ApplySpellRES("B3EMPTY",Myself) // Absolutely empty spell, with a useless effect: // (Opcode #0 with all fields 0'd, Target=Self, Probability 1=100) MakeGlobal() // Non-instant action, allows our spell to apply and gets the engine to realize // I am no longer a controlled creature. Familiars must also be global. AddFamiliar() // Actually get the engine to promote me into being a familiar. ChangeEnemyAlly(Myself,FAMILIAR) // Remember that I am a familiar (see below). ApplySpellRES("B3EMPTY",Myself) // AddFamiliar() is buggy and clears all of my ai-type values (except EA) // until I am updated, force update. END Note that AddFamiliar() screws with the creature's GENERAL in an unrecoverable way, so that value will be lost upon reload. Other than that, I believe the above works as intended.
  4. Triggers with IDS values < 0x4000 use an alternate event-driven system, which is buggy even for IE standards. A negated event trigger returns true if there are pending events that have yet to be processed, and if any of these pending events fails to satisfy the unnegated trigger. You can see this effect by putting !OnCreation() on a creature. The block will fire every time the creature receives an event other than the one that is defined, such as taking damage.
  5. Delay(intArg1) is just the total number script passes performed on the current creature, (including the one in progress), modulus intArg1. Very simple implementation in the engine: return m_nExpectedProcessPendingTriggersCalls % intArg1 <= m_nMissedProcessPendingTriggerCalls Unless an action specifically allows for itself to be interrupted, a currently executing action will block script passes for its duration, but not stop these blocked passes from being counted in m_nExpectedProcessPendingTriggersCalls. TL;DR: Delay() should really be called something like "Interval()" — and this "interval" can be missed if the script is preoccupied with something else when it would otherwise be hit, as is standard behavior with IE scripting. --- And yes, scripting uses the same random value to seed all RandomNum() triggers across a single tick; if you have multiple RandomNum() calls with the same parameters, they will all generate the same result.
  6. To be clear, Detect() has no problem detecting invisible creatures, as evidenced by it working "correctly" when using object selectors, (eg. [ANYONE]). NearestEnemyOf(), however, will not match an invisible creature unless the caller is under op193 (Invisible Detection by Script). I suspect this is true for all/most of the Nearest objects.
  7. There's three major problems I can see with the MDR INI files: 1) They are using the wrong animation header, [multi_new], when it should be [monster_multi]. The engine ignores everything under an incorrect header, so nothing you input here will be considered without first correcting the section header. 2) split_bams is hooked up to false_color internally, most likely a copy+paste error in the source. Meaning that if you correct the section header, it is impossible to designate split_bams=1, (the engine will execute this as false_color=1), and thus dragon animations (as they stand) will be in the wrong animation format and won't render. 3) palette[1-5] requires an internal field, m_bNewPalette, to be flipped in order to function. It is impossible to set this field via the INI, and so palette[1-5] are effectively defunct. Note that the engine hardcodes all of these fields correctly for the different dragon animations if [monster_multi] isn't defined, so that's why everything works if you don't mess with the INI files.
  8. 1) Weapon abilities, (right-click quick weapon in inventory -> Abilities), or right-click weapon in actionbar, (F2-F5 depending on class). Only functions in a weapon's item ability header. 2) Spell, (F7 in actionbar). Only functions in a spell's ability header. 3) Item, (F8 in actionbar). Only functions in an item's ability header. 4) Ability, (F12 in actionbar). Only functions in a spell's ability header. Other values do not function, and the associated ability will not appear anywhere. The only flexibility of this field is being able to change where spells appear, (Spell vs Ability) — and, on weapons, differentiating between weapon abilities and item abilities. Otherwise, you are locked to the relevant type. So, pretty straightforward.
  9. I've looked into this, and, yep, it's bugged. Here's pseduocode of what the engine does if there's an enemy in sight of the character hiding, (using the nearest enemy): So, first off, it's extremely hard to hide while an enemy is around. You have to pass two insane checks, the only saving grace is that they can each be disabled if the enemy has the counter-condition, (being deaf or blind). From the pseduocode, the MOVESILENTLY check was inverted, so a lower(!) MOVESILENTLY skill value was better here. I've attached an exe-patch that fixes that condition, but it is still insanely hard to hide while enemies are nearby; by design, I guess? bubb_fix_hide.zip
  10. The engine is hardcoded to deactivate modals whenever the creature starts taking another action. There is a small list of (hardcoded) actions the engine will allow to be started without disrupting modals: 0 NoAction 18 Hide 22 MoveToObject 23 MoveToPoint 63 Wait 83 SmallWait 84 Face 89 Follow 90 MoveToPointNoRecticle 93 LeaveAreaName 99 WAITINLINE (unlisted, defunct) 215 FollowObjectFormation
  11. It appears IWD:EE lets you donate at temples: However, IWD:EE only lets you boost your reputation to 8 using donations, so it's pretty much a moot mechanic unless you need to salvage your reputation in case you killed the wrong person.
  12. CHASE.IDS is a bit complicated — there are many edge cases and hardcoded exceptions. When a creature is in an area that is being unloaded, (for example, by all party members leaving a non-master area, or transitioning to a new master area), the engine allows creatures to follow the party to the new area. In general, if a creature is executing an action from CHASE.IDS while the area it is in is being unloaded, it is allowed to follow its target through the transition.
  13. EEex is an exe hack and thus it doesn't work anywhere except the latest EE versions on Windows. Note some of the functionality could be added to GemRB easily, (the Opcode parameter changes especially), but the whole Lua-scripting and memory editing portions are totally platform / engine specific. It really wouldn't work.
  14. It's easier just to show the flaw in the trigger block evaluation code. if (hasNextTriggerObjectOverride) { if (nextTriggerObjectOverride != NULL) { // do eval stuff hasNextTriggerObjectOverride = false } } else { // do eval stuff } NextTriggerObject sets both hasNextTriggerObjectOverride=true, and if it can't find a valid object, nextTriggerObjectOverride=NULL. Once this happens, the engine gets stuck in a bad state. Since nextTriggerObjectOverride is NULL it never clears hasNextTriggerObjectOverride, and it forever skips evaluating further triggers, (in the current trigger block). Note though, while it's not evaluating the triggers, it is still running through all of them and doing janitorial actions. Meaning - every non-OR'd trigger still sets the whole block's result to false, the active OR count still ticks down - another NextTriggerOverride has the potential of fixing the deadlock, etc. The only way a trigger block can still succeed after NextTriggerOverride breaks is: The NextTriggerOverride was in an OR block There are no subsequent triggers after the OR block A trigger in the OR block, that is positioned above the NextTriggerOverride, already evaluated to true or, further in the same OR block, another NextTriggerOverride evaluates to a valid creature, and fixes the bad state. Once that happens, the trigger block will start evaluating normally again from that point onward. So, I suppose, one way to prevent NextTriggerOverride from breaking everything would be something like this: IF OR(3) TriggerOverride(Player6,Global("B3WEIRD","LOCALS",1)) TriggerOverride(Myself,False()) // This will fix the deadlock // Whatever trigger here THEN
  15. Most of the spell protection opcodes add an entry to an immunity list in the stats of a creature. Every time the effects list is evaluated on a creature the engine checks if one of these lists is populated, and if it is it adds a corresponding graphic to the creature. Pseudocode: Opcode #291 sets m_bPreventSpellProtectionEffects to Param2, (so it's an all-or-nothing deal). The list of Opcode graphics it blocks is as follows: // Blocks the below graphics m_bPreventSpellProtectionEffects -> Opcode #291 Param2 // Applies SPTURNI2 m_cBounceProjectile -> Opcode #197 m_cBounceEffect -> Opcode #198 m_cBounceProjectileLevelDec -> Opcode #200 m_cBounceSchool -> Opcode #202 m_cBounceSecondaryType -> Opcode #203 m_cBounceSpell -> Opcode #207 m_cImmunitiesSecondaryTypeLevelDec -> Opcode #226 m_cBounceSchoolLevelDec -> Opcode #227 m_cBounceSecondaryTypeLevelDec -> Opcode #228 m_nChaosShield -> Opcode #299 Param1 // Applies SPMAGGLO m_cImmunitiesProjectileLevelDec -> Opcode #201 m_cImmunitiesSchool -> Opcode #204 m_cImmunitiesSecondaryType -> Opcode #205 m_cImmunitiesSchoolLevelDec -> Opcode #223 m_cSpellTrapLevelDec -> Opcode #259 The IESDP description lists Opcode #199 as one of the opcodes with blocked graphics - but this is false, (that opcode has no associated graphics). So this is all to say, Opcode #291 doesn't discriminate which visuals it blocks; if you apply it to a creature with Param2 = 1, all the above opcodes will have their graphics suppressed for as long as the Opcode #291 stays in effect. If you put a permanent Opcode #291 on every creature, and manually add-back the graphics to all the affected spells, in theory you could customize how you want new spells to display without borking the vanilla ones.
×
×
  • Create New...