Miscellaneous
JumpToSpecificHouse(displayName, houseId)
PreviewItemLink(itemLink, dyeBrushId)
GetItemLinkGrantedRecipeIndices(itemLink) – recipeListIndex, recipeIndex
InvitationNotFound wrote: »Hi guys
As the author of this addon I might add / clarify a few things. Btw. you will find a link in my signature to the thread i created here on the forum where I've introduced the addon.
In the German thread about the addon, someone tried to argue about it in a similar way as the OP does here (ZOS didn't care btw.).
The point is that ZOS implemented the specific API a while ago (after the lunch of homestead, so this was a feature that has been introduced at a later point in time). See this thread:
https://forums.elderscrollsonline.com/en/discussion/335644/update-14-api-patch-notes-change-log-ptsMiscellaneous
JumpToSpecificHouse(displayName, houseId)
PreviewItemLink(itemLink, dyeBrushId)
GetItemLinkGrantedRecipeIndices(itemLink) – recipeListIndex, recipeIndex
So ZOS explicitly made this functionality available to addon authors. Why should they make this available when they don't want people to use it? This wouldn't make much sense.
So what we have here is functionality provided by ZOS that has been announced on the forums. Of course, you may not like it and you may complain and tag some ZOS employees. I guess that's your right. I just don't think that will change anything as this decision has been made by ZOS.
If you do not want people in your house, please adjust the rights of your house to prevent people from visiting them. That's what ZOS wants (imho).
edit: "deleted" the OP line as I've misread it the first time. I hope this post answers your questions to a certain degree.
To be honest.. I highly doubt you will get an actual answer on this.
On another note, it appears that any time that Zos does not like what an addon does - they intentionally break it by changing the API. So that's the most likely thing to happen if they don't like it. I've never heard of anyone being banned for using an addon, even ones Zos has intentionally broken.
They probably don't say "Yeah it's fine to use!" since they may change their mind later about it.
To be honest.. I highly doubt you will get an actual answer on this.
On another note, it appears that any time that Zos does not like what an addon does - they intentionally break it by changing the API. So that's the most likely thing to happen if they don't like it. I've never heard of anyone being banned for using an addon, even ones Zos has intentionally broken.
They probably don't say "Yeah it's fine to use!" since they may change their mind later about it.
I feel as though the ability to port to other people's publicly accessible, second (or third or tenth) home was lacking from the initial implementation of player housing. I feel like, so long as the API respects the home owners' permission settings (which the API does so far as I have seen), this is a great addition that fills a gap in the existing functionality.
I hope that they keep this add on and the supporting API the same.
InvitationNotFound wrote: »Hi guys
As the author of this addon I might add / clarify a few things. Btw. you will find a link in my signature to the thread i created here on the forum where I've introduced the addon.
In the German thread about the addon, someone tried to argue about it in a similar way as the OP does here (ZOS didn't care btw.).
The point is that ZOS implemented the specific API a while ago (after the lunch of homestead, so this was a feature that has been introduced at a later point in time). See this thread:
https://forums.elderscrollsonline.com/en/discussion/335644/update-14-api-patch-notes-change-log-ptsMiscellaneous
JumpToSpecificHouse(displayName, houseId)
PreviewItemLink(itemLink, dyeBrushId)
GetItemLinkGrantedRecipeIndices(itemLink) – recipeListIndex, recipeIndex
So ZOS explicitly made this functionality available to addon authors. Why should they make this available when they don't want people to use it? This wouldn't make much sense.
So what we have here is functionality provided by ZOS that has been announced on the forums. Of course, you may not like it and you may complain and tag some ZOS employees. I guess that's your right. I just don't think that will change anything as this decision has been made by ZOS.
If you do not want people in your house, please adjust the rights of your house to prevent people from visiting them. That's what ZOS wants (imho).
Interesting, I wonder whether this is stable and will make me crash or if its worst installing
I feel as though the ability to port to other people's publicly accessible, second (or third or tenth) home was lacking from the initial implementation of player housing. I feel like, so long as the API respects the home owners' permission settings (which the API does so far as I have seen), this is a great addition that fills a gap in the existing functionality.
I hope that they keep this add on and the supporting API the same.
InvitationNotFound wrote: »Interesting, I wonder whether this is stable and will make me crash or if its worst installing
In the current state I consider it stable. There shouldn't be crashes or error message. If you discover any issues, please post your feedback either on the esoui addon page or on the addon thread i started here on the forums and i'll look into it as soon as possible.I feel as though the ability to port to other people's publicly accessible, second (or third or tenth) home was lacking from the initial implementation of player housing. I feel like, so long as the API respects the home owners' permission settings (which the API does so far as I have seen), this is a great addition that fills a gap in the existing functionality.
I hope that they keep this add on and the supporting API the same.
Yes, this is missing in the base game and i was surprised that the API for it exists. The addon respectively the API respects the permissions. It's a bit of a pain as the API is poorly written in my opinion and as an author, the control i have about return values or about the things that are happening (is it possible to port) are very restricted. E.g. it is not possible to query which houses a player owns, which means that I have to display always all houses in the dropdown.
Anyway, I might add a new feature soon after the pvp event (which sucks, but consumes a lot of my time >_<).
InvitationNotFound wrote: »Hi guys
As the author of this addon I might add / clarify a few things. Btw. you will find a link in my signature to the thread i created here on the forum where I've introduced the addon.
In the German thread about the addon, someone tried to argue about it in a similar way as the OP does here (ZOS didn't care btw.).
The point is that ZOS implemented the specific API a while ago (after the lunch of homestead, so this was a feature that has been introduced at a later point in time). See this thread:
https://forums.elderscrollsonline.com/en/discussion/335644/update-14-api-patch-notes-change-log-ptsMiscellaneous
JumpToSpecificHouse(displayName, houseId)
PreviewItemLink(itemLink, dyeBrushId)
GetItemLinkGrantedRecipeIndices(itemLink) – recipeListIndex, recipeIndex
So ZOS explicitly made this functionality available to addon authors. Why should they make this available when they don't want people to use it? This wouldn't make much sense.
So what we have here is functionality provided by ZOS that has been announced on the forums. Of course, you may not like it and you may complain and tag some ZOS employees. I guess that's your right. I just don't think that will change anything as this decision has been made by ZOS.
If you do not want people in your house, please adjust the rights of your house to prevent people from visiting them. That's what ZOS wants (imho).
Thanks. Has this addon revealed itself to make people crash ? or the fact that it is only active during TP phase make it safe to use without creating other issues ?
Nice contribution for the community thanks ))