"Prefixes cannot be changed" does not do what it says.

So I learned yesterday the hard way that "Prefixes cannot be changed" does not actually do what one might think it does and lost 2ex in SSF.

What I thought it does:
- prefixes cannot be removed
- prefixes cannot be added
- prefixes cannot have their values changed

What it actually does
- prefixes cannot be removed
- prefixes CAN be added
- prefixes cannot have their values changed

My logic was:
- I have a left and right pocket.
- I have a red carrot and a green apple in the left pocket.
- I say "the contents of my left pocket cannot change"
- What of these situations would you consider a change from a red carrot and a green apple?
--- There is now only a red carrot
--- There is now an blue carrot and a black apple
--- There is now a red carrot, a green apple and a huge diamond
- Personally I think every person would consider an extra huge diamond a change.

So, GGG, please
change the way "Prefixes cannot be changed" works, or
rename it to "prefixes cannot be removed and their values cannot be changed"


If you would like to see my experience: https://www.youtube.com/watch?v=4p0kCtpkBLc

"

drklrd wrote:

Prefixes cannot be changed = Existing Prefixes cannot be changed

- I have a left and right pocket. === ok
- I have a red carrot and a green apple in the left pocket. ===ok
- I say "the contents of my left pocket cannot change" === wrong wording. you should of said "my red carrot and green apple cannot change". It doesn't mean that you can't add a nectarine to your left pocket.


I think the wording is fine, and I would not have them changed.

semantics unclear

autism intensifies

"

drklrd wrote:

Prefixes cannot be changed = Existing Prefixes cannot be changed

Yeah, that's the problem...

"

drklrd wrote:

I think the wording is fine, and I would not have them changed.

... yet you say there is no problem.

....

Say an Item has:
[Prefix filled: ABC]
[Prefix filled: DEF]
[Prefix empty]
[Suffix filled]
[Suffix filled]
[Prefixes cannot be changed]

If "Prefixes cannot be changed" meant the empty one could not be filled, then an Exalt would do nothing... Which is fine, but just so we're on the same page.

Now a Chaos Orb would have the following effect:
[Prefix ABC]
[Prefix DEF]
[NEW PREFIX] or [Prefix Empty]
[...(0-3) Suffixes...]

OP is saying he'd always expect "Prefix Empty" to be the result (never the "NEW PREFIX" result). The problem comes from thinking of a prefix as its SLOT -- rather than thinking of the prefix as what goes into the prefix slot (a prefix)... which, I think, is reasonable.

Edit: Essentially, OP counts a null prefix as a prefix.

I have no intention to argue. I just provided my feedback.
I would just like to say that if it happened to me, it may happen to other players and it was not a pleasant experience.
The fewer chances for a misunderstanding the better.
And as this is the most expensive common craft (Hits can't be evaded is specific) I think it deserves a few more words as description.

Op is right, it is misleading. And it would cost nothing to add "existing" to it so why not.

"

drklrd wrote:

"

etkratos wrote:

Op is right, it is misleading. And it would cost nothing to add "existing" to it so why not.

Because changing its name is not a solution. It should have a wiki description about what it does, there should be a campaign tutorial on how to craft.


The whole definition for the craft is

"

One can utilize the Prefixes/Suffixes Cannot Be Changed meta-crafting mod to protect them while altering the item.

And even if you put that in the description you now have to explain what meta-crafting is, what altering is, what happens when it interacts with items that make altering impossible (corruption), then you need to explain tags visible and hidden.


So no, changing the name is not a solution.

"General! Should we spare this tiny village? There are only civilians and it's not even in our way."

"No! Burn it down and kill everyone! If we can't achieve World Peace right at this moment, nothing else matters!"