New Engine Feature: Add an option to make op65 truly cosmetic#107
Open
4Luke4 wants to merge 1 commit into
Open
New Engine Feature: Add an option to make op65 truly cosmetic#1074Luke4 wants to merge 1 commit into
4Luke4 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This tweak will allow modders to safely use
op65as a purely cosmetic effect (i.e., without confusing the AI with an undispellable/fakeSTATE_BLUR... Also relevant for vanilla Cloak of Displacement item...).@Bubb13
I initially thought this was kinda easy to implement, but it turned out a complex task due to those damned
.EFFfiles (as you said multiple times,op177/182/183/283drive theEFFfile instead of going through the normal effect application process... As a result, please make sure everything is indeed correct...).Feature tested on: IWD:EE
v2.6.6.0.