pete_smith1229 Posted October 22, 2022 Share Posted October 22, 2022 Using NI, I've created a spell for IWD:EE which causes stun using opcode "Stun (45)". I created another spell which is supposed to remove the portrait icon for stun but it doesn't seem to work. I've tried both opcodes "Remove portrait icon (240)" and "Prevent portrait icon (169)" but the stun icon is always present until the duration. Any advice? Quote Link to comment
subtledoctor Posted October 22, 2022 Share Posted October 22, 2022 It might be a hardcoded part of the stat associated with the Stun effect? I don't remember. Quote Link to comment
CamDawg Posted October 22, 2022 Share Posted October 22, 2022 Stun is an opcode, like sleep or poison, where you can attach a portrait icon to the effect directly in the special field on the EEs. If that's the case, the icon won't go away unless you're curing the underlying stun. Quote Link to comment
pete_smith1229 Posted October 22, 2022 Author Share Posted October 22, 2022 @CamDawg Thanks. Funnily enough, sleep and poison have an "icon" field where you can select the portrait icon and these can be removed without curing the status. Stun doesn't have an icon field so I wonder why some status conditions have this and others dont... Quote Link to comment
Bubb Posted October 22, 2022 Share Posted October 22, 2022 (edited) The answer to "why doesn't an opcode do X" is pretty much that the devs never intended for it to be used that way. And yeah, I can confirm that op45 has no Special field functionality; it will continuously apply STATDESC.2DA["BAM_FILE", 55] while the target is alive. Edit: And I don't think you can clear that cell to remove the icon. The engine falls back to [STATES.BAM, sequence=row+65, frame=0] when it encounters a default value. Edited October 22, 2022 by Bubb Quote Link to comment
polytope Posted October 23, 2022 Share Posted October 23, 2022 Note that many stun effects have a #142 : display portrait icon - stun tacked on, it's unnecessary as the portrait icon is automatically displayed as part of the opcode, as others have said. Also, generally speaking with opcodes that trigger an associated string, icon or other secondary effect (such as the brief glow from #175), immunity to the string, icon or whatever is usually disregarded. Quote Link to comment
pete_smith1229 Posted October 24, 2022 Author Share Posted October 24, 2022 Thanks all, this is very insightful. Wasn't aware that some opcodes are more of less generally hard-coded with certain triggers. Sounds like it would be too much trouble in trying to remove the stun icon so will leave it at that Quote Link to comment
Recommended Posts
Join the conversation
You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.