#secondaryeffectalways?

[zepath]

More like #secondaryeffectnever

I have tried on a number of occasions to get this command to work properly, but the numbers I input for it (the full command being #secondaryeffectalways <effect nbr>) do no correspond with the effects listed in the mod manual or with the weapon numbers (as secondary effects are essentially weapons stacked on top of weapons). For example, attempting to give a weapon the constant secondary effect of "Small Area Fire" I use #secondaryeffectalways 171 (as the mod manual says and as common sense dictates since weapon number 171 is Small Area Fire), yet the resulting weapon ends up with some strange effect like "Flail" instead. What gives, eh?

[HoneyBadger]

Somewhere in all that code, there must be a bug that's acting like a switch. When you put in that command, the computer looks at it, sees something it's not supposed to see, and switches to the next effect, "next" being in this case whatever random effect is close at hand. Computers are a wonderful example of chaos theory. Technically, nothing should go wrong with them. Realistically, everything does

[FrankTrollman]

The actual command is

#secondaryeffect <effect nbr>

The "always" in there is not necessary and doesn't do anything except break the syntax. It's a glitch in the mod manual.

-Frank

[Foodstamp]

FrankTrollman said:
The actual command is

#secondaryeffect <effect nbr>

The "always" in there is not necessary and doesn't do anything except break the syntax. It's a glitch in the mod manual.

The Great Catsby has spoken.

fixt

[zepath]

So the whole thing is just a clever ruse to make me think there was a way to mod constant secondary effects. I believe the following expression sums up my feelings on the matter...

"This blows."

[Endoperez]

It seems that #secondaryeffectalways doesn't work, but I don't know why Frank thinks it isn't supposed to work.