If I may posit my own theory, I would suggest the reason is as stated--to be annoying. It seems quite clear that they don't want you to cross the pantheon, and doing so even in the small ways they let you, is intended to be punishing in at least some form.
Now this may make me sound dickish, but I'll say it anyway. It's like a dungeon master in D&D or whatever that creates an item for a player and points them to a set path for them to use it, and then the player says no and goes to use the item for their own gain. In retaliation, the DM punishes that player through indirect methods/sheer inconvenience.
I've seen it before and hell, I even did something similar myself in my earlier years of DMing at 16 or so. It's just salty DMing, and a pretty minor form of it at that. It's quite literally one of the most common occurrences in tabletop gaming, and even though this isn't literal tabletop, it's got damn near every element of it. Only makes sense that it'd include the more common downsides from time to time, too.
Though please note, I'm not intending to say this is malicious treatment by the devs, but rather mostly just a dismissal of the subject. Dismissal, by definition, is "the act of treating something as unworthy of serious consideration." I'd certainly say "no and no" qualifies, but as I understand it, the explanation has already been given before. Dismissal may be justified in this case. I'm not here to judge on that.
Even if it's as simple as "you better take that sword off first or I'll mess with it," a punishment is still a punishment. I've seen it said that it's because she refuses to let you walk around with her relic in a corrupted state, right in front of her eyes. If that's their justification, that's it.
Though I don't agree with it, it seems to be something they're set in stone on. I'd just relent and let it be. If you have her corrupted sword, you clearly aren't a Lumite? Lumiatite? Lumi'ite? Whatever. You clearly don't RP her as your patron goddess, so how often are you really going to go see her and have to worry about it? Sure it's tedious, but it does seem to be making a mountain out of a molehill a little bit.
Now this may make me sound dickish, but I'll say it anyway. It's like a dungeon master in D&D or whatever that creates an item for a player and points them to a set path for them to use it, and then the player says no and goes to use the item for their own gain. In retaliation, the DM punishes that player through indirect methods/sheer inconvenience.
I've seen it before and hell, I even did something similar myself in my earlier years of DMing at 16 or so. It's just salty DMing, and a pretty minor form of it at that. It's quite literally one of the most common occurrences in tabletop gaming, and even though this isn't literal tabletop, it's got damn near every element of it. Only makes sense that it'd include the more common downsides from time to time, too.
Though please note, I'm not intending to say this is malicious treatment by the devs, but rather mostly just a dismissal of the subject. Dismissal, by definition, is "the act of treating something as unworthy of serious consideration." I'd certainly say "no and no" qualifies, but as I understand it, the explanation has already been given before. Dismissal may be justified in this case. I'm not here to judge on that.
Even if it's as simple as "you better take that sword off first or I'll mess with it," a punishment is still a punishment. I've seen it said that it's because she refuses to let you walk around with her relic in a corrupted state, right in front of her eyes. If that's their justification, that's it.
Though I don't agree with it, it seems to be something they're set in stone on. I'd just relent and let it be. If you have her corrupted sword, you clearly aren't a Lumite? Lumiatite? Lumi'ite? Whatever. You clearly don't RP her as your patron goddess, so how often are you really going to go see her and have to worry about it? Sure it's tedious, but it does seem to be making a mountain out of a molehill a little bit.
