Dragonnord wrote: »ZOS has nothing to do with this. If one simple word, symbol or value in a code helps fixing something in the game and break addons then so be it. I prefer the game fixed than addons working or breaking.
Addons creators should go and update their addons, instead of ZOS coding around addons.
lordrichter wrote: »Dragonnord wrote: »ZOS has nothing to do with this. If one simple word, symbol or value in a code helps fixing something in the game and break addons then so be it. I prefer the game fixed than addons working or breaking.
Addons creators should go and update their addons, instead of ZOS coding around addons.
This broke addons that were updated for Wrathstone. This is not lazy addon writer syndrome.
lordrichter wrote: »Dragonnord wrote: »ZOS has nothing to do with this. If one simple word, symbol or value in a code helps fixing something in the game and break addons then so be it. I prefer the game fixed than addons working or breaking.
Addons creators should go and update their addons, instead of ZOS coding around addons.
This broke addons that were updated for Wrathstone. This is not lazy addon writer syndrome.
Dragonnord wrote: »lordrichter wrote: »Dragonnord wrote: »ZOS has nothing to do with this. If one simple word, symbol or value in a code helps fixing something in the game and break addons then so be it. I prefer the game fixed than addons working or breaking.
Addons creators should go and update their addons, instead of ZOS coding around addons.
This broke addons that were updated for Wrathstone. This is not lazy addon writer syndrome.
What? I didn't say ANYTHING about lazy addon syndrome. I said ZOS can't work around addons, they work around the game, and if addons get broken then addons creators should update them (as they always do).
Dragonnord wrote: »lordrichter wrote: »Dragonnord wrote: »ZOS has nothing to do with this. If one simple word, symbol or value in a code helps fixing something in the game and break addons then so be it. I prefer the game fixed than addons working or breaking.
Addons creators should go and update their addons, instead of ZOS coding around addons.
This broke addons that were updated for Wrathstone. This is not lazy addon writer syndrome.
What? I didn't say ANYTHING about lazy addon syndrome. I said ZOS can't work around addons, they work around the game, and if addons get broken then addons creators should update them (as they always do).
Except, in this case, it literally is a mistake/bug on ZOS's end.
sirinsidiator wrote: »They removed an API method, but also added a replacement function for addons. Unfortunately they made a small mistake in that replacement, which is why we see this error.
I've made an update for Medic which includes a fix for this problem and uploaded it to dropbox (as it is untested). Let me know if it works and I'll upload it to ESOUI later.
Dragonnord wrote: »Dragonnord wrote: »lordrichter wrote: »Dragonnord wrote: »ZOS has nothing to do with this. If one simple word, symbol or value in a code helps fixing something in the game and break addons then so be it. I prefer the game fixed than addons working or breaking.
Addons creators should go and update their addons, instead of ZOS coding around addons.
This broke addons that were updated for Wrathstone. This is not lazy addon writer syndrome.
What? I didn't say ANYTHING about lazy addon syndrome. I said ZOS can't work around addons, they work around the game, and if addons get broken then addons creators should update them (as they always do).
Except, in this case, it literally is a mistake/bug on ZOS's end.
What do you mean?
sirinsidiator wrote: »They removed an API method, but also added a replacement function for addons. Unfortunately they made a small mistake in that replacement, which is why we see this error.
I've made an update for Medic which includes a fix for this problem and uploaded it to dropbox (as it is untested). Let me know if it works and I'll upload it to ESOUI later.
ChuckyPayne wrote: »Without addons is it still a problem?
Dragonnord wrote: »ChuckyPayne wrote: »Without addons is it still a problem?
Not at all. Absolutely NO problems without addons.
And they say ZOS is the problem, haha!
Update addons. It has ALWAYS been that way!!! Creators update the addons after patches.
I don't know why this time it has to be different. Only because a tiny patch broke them?
Update addons.
Dragonnord wrote: »ChuckyPayne wrote: »Without addons is it still a problem?
Not at all. Absolutely NO problems without addons.
And they say ZOS is the problem, haha!
Update addons. It has ALWAYS been that way!!! Creators update the addons after patches.
I don't know why this time it has to be different. Only because a tiny patch broke them?
Update addons.
sirinsidiator wrote: »They removed an API method, but also added a replacement function for addons. Unfortunately they made a small mistake in that replacement, which is why we see this error.
I've made an update for Medic which includes a fix for this problem and uploaded it to dropbox (as it is untested). Let me know if it works and I'll upload it to ESOUI later.
Dragonnord wrote: »And they say ZOS is the problem, haha!
anitajoneb17_ESO wrote: »Dragonnord wrote: »ChuckyPayne wrote: »Without addons is it still a problem?
Not at all. Absolutely NO problems without addons.
And they say ZOS is the problem, haha!
Update addons. It has ALWAYS been that way!!! Creators update the addons after patches.
I don't know why this time it has to be different. Only because a tiny patch broke them?
Update addons.
Yes, it is ZOS' fault if they break addons. Addons are a nice, customizable addition to the game which costs NOTHING to ZOS and enhances the game exprience of many of us, bringing ZOS money. I would have quit ESO for years if I had had to play without addons, and I'm surely not the only one.
You're being very unfair. Fortunately, ZOS is quite fair. With the exception of today's incident, ZOS takes quite good care of addon authors, and they even have a developer mostly dedicated to the API, the add-on compatibility, and managing the community of addon coders. His name is Chips_something ( I don't remember ;-) )
Dragonnord wrote: »Game first, addons after.
Dragonnord wrote: »anitajoneb17_ESO wrote: »Dragonnord wrote: »ChuckyPayne wrote: »Without addons is it still a problem?
Not at all. Absolutely NO problems without addons.
And they say ZOS is the problem, haha!
Update addons. It has ALWAYS been that way!!! Creators update the addons after patches.
I don't know why this time it has to be different. Only because a tiny patch broke them?
Update addons.
Yes, it is ZOS' fault if they break addons. Addons are a nice, customizable addition to the game which costs NOTHING to ZOS and enhances the game exprience of many of us, bringing ZOS money. I would have quit ESO for years if I had had to play without addons, and I'm surely not the only one.
You're being very unfair. Fortunately, ZOS is quite fair. With the exception of today's incident, ZOS takes quite good care of addon authors, and they even have a developer mostly dedicated to the API, the add-on compatibility, and managing the community of addon coders. His name is Chips_something ( I don't remember ;-) )
I didn't say anything about or against addons creators, at all, I just say the game goes first, and if a change fixes something in the game and breaks an addon, I take it anyways.
And I DO NOT agree that is ZOS fault if addons get broken.
Game first, addons after.
StytchFingal wrote: »With this Craftstore and Dolgubon's worked well enough to do writs, thanks!
Dragonnord wrote: »anitajoneb17_ESO wrote: »Dragonnord wrote: »ChuckyPayne wrote: »Without addons is it still a problem?
Not at all. Absolutely NO problems without addons.
And they say ZOS is the problem, haha!
Update addons. It has ALWAYS been that way!!! Creators update the addons after patches.
I don't know why this time it has to be different. Only because a tiny patch broke them?
Update addons.
Yes, it is ZOS' fault if they break addons. Addons are a nice, customizable addition to the game which costs NOTHING to ZOS and enhances the game exprience of many of us, bringing ZOS money. I would have quit ESO for years if I had had to play without addons, and I'm surely not the only one.
You're being very unfair. Fortunately, ZOS is quite fair. With the exception of today's incident, ZOS takes quite good care of addon authors, and they even have a developer mostly dedicated to the API, the add-on compatibility, and managing the community of addon coders. His name is Chips_something ( I don't remember ;-) )
I didn't say anything about or against addons creators, at all, I just say the game goes first, and if a change fixes something in the game and breaks an addon, I take it anyways.
And I DO NOT agree that is ZOS fault if addons get broken.
Game first, addons after.
If addons were broken if ZOS decides to do things differently, yes, I would not fault ZOS.
If addons were broken if the code that ZOS provides for addons to use contain an error--not a design change, but an actual error like the kind that would cost you points on your homework if this were school--then the fault is completely ZOS's.
You really should take a moment to understand what's going on before making further silly statements.
Dragonnord wrote: »Repair your addons. Period. ZOS will not re-roll because of you.
Sanctuary_Reaper wrote: »Yeps same, add ons affected, but thats not zos's fault, however when you get a boat load of errors for simply buying a horse upgrade, they have messed something up.
And dont be surprised at there special brand of communication on any of this, "SILENCE"
Dragonnord wrote: »Not at all. Absolutely NO problems without addons.
And they say ZOS is the problem, haha!
/script d(GetCraftingSkillLineIndices(CRAFTING_TYPE_BLACKSMITHING))ZOS code doesn't call this function, that's why you don't see any errors without addons, unless you invoke the /script command. The sole purpose of compatibility replacement is to not break addons using removed API. It failed to deliver.