Go to Page... |
Compatibility: | Firesong (8.2.5) Lost Depths (8.1.5) High Isle (8.0.0) Ascending Tide (7.3.5) Deadlands (7.2.5) Waking Flame (7.1.5) Blackwood (7.0.5) Greymoor (6.0.5) |
Updated: | 11/28/22 03:26 PM |
Created: | 11/16/22 10:52 PM |
Monthly downloads: | 84 |
Total downloads: | 3,121 |
Favorites: | 2 |
MD5: | |
Categories: | PvP, Combat Mods |
![]() |
Comment Options |
adjutant |
View Public Profile |
Send a private message to adjutant |
Find More Posts by adjutant |
Add adjutant to Your Buddy List |
Busygeezus |
View Public Profile |
Send a private message to Busygeezus |
Find More Posts by Busygeezus |
Add Busygeezus to Your Buddy List |
Xorzoo |
View Public Profile |
Send a private message to Xorzoo |
Send email to Xorzoo |
Find More Posts by Xorzoo |
Add Xorzoo to Your Buddy List |
![]() |
||
|
But the addon code that will be created is personal property of the respective persons. You cannot just copy anything and provide a new name, even though you might have fixed or added stuff yourself. It does not matter if you think/know the code was broken and you fixed it. You need to keep the names, and provide credit if you copy something. And you need to ask for permissions as this is "intellectual property" (unless the developer has explicitly allowed up in advance by writing this to the addon files, comments, documentation, wiki, github repo etc.). Just beause something is globally accessible it does not mean you have the right to touch and use it. Would you open the door of a parked car, if it was forgotten to be locked, and change the settings of that car, maybe even remove some parts and add your own cosy seat pad, and afterwards drive around with it as you "say it is yours now"? Maybe not the best example but it should explain what one would/should not do ![]() Let's wait for the addon dev feedback and if there is none just keep it. For the next time please just respect this in advance OR just keep the name and add soemthing like "Updated" / "Fixed" to the end, if you cannot contact the original dev and ask for maintenance/addition to the original addon team. This always is easier as it keeps the users and unstresses updates.
Last edited by Baertram : 11/18/22 at 01:27 PM.
|
|
![]() |
![]() |
Baertram |
View Public Profile |
Send a private message to Baertram |
Send email to Baertram |
Find More Posts by Baertram |
Add Baertram to Your Buddy List |
![]() |
||||
|
![]() But rule are rules.
I saw you wrote addon yourself so you probably know this already, all those addons are pretty much using the same code at core. Is that because they copy each other with new name or because this is exactly how ZOS allows to interact with game client? ![]()
|
|||
![]() |
![]() |
Xorzoo |
View Public Profile |
Send a private message to Xorzoo |
Send email to Xorzoo |
Find More Posts by Xorzoo |
Add Xorzoo to Your Buddy List |
![]() |
|||
|
Hi Xorzoo,
thanks for your answer.
![]() It's common sense, or at least should be, and ESOUI likes to follow this. If the author does not respond within a few weeks it's fine, we assume he/she is missing in action and thus the original addon is dead and someone can take over officially (unless no written text says not to do so please, or licensing is asking to not do it that way). I neither found any licensing, correct.
If you want to ge the credits and fame for your work, which is understandable, add yourself to the official addon's team and add your name to the addon's txt files and description, but do not simply change the addon name please. It makes no difference if you change a lot of the code, the idea and original addon were his idea and code. Giving credit as you did is nice and should be normal, right. But copying an addon without asking should not happen unless the original dev(s) allow you to do so. As the patch section of "other files" is enabled at the original addon (and I assume this was on purpose and not forgotte to disable as it's enabled for each new addon by default), and as GitHub exists and was linked, I assume it's okay for the author. But asking is better then not doing it. So all I wanted to know here is that everything was done where the original dev could disagree. If we get no answer, go ahead and keep it. The userbase will like a working addon ![]() Thanks for your understanding. P.S. Please add the dependencies needed to the addon description so the users know what to install with that addon, e.g. LibAddonMenu-2.0. Thank you
Last edited by Baertram : 11/18/22 at 01:59 AM.
|
||
![]() |
![]() |
Baertram |
View Public Profile |
Send a private message to Baertram |
Send email to Baertram |
Find More Posts by Baertram |
Add Baertram to Your Buddy List |
![]() |
||
|
I have sent the original author a message as requested, but I don't change a line and release it as a new addon, do a diff and see what is actually going on. For example: Fixed one hand/shield not working Fixed potion detection failed due to API changes, Fixed gear detection failed likely due to API changes as well, Fixed pvp only mode New Feature: added in-combat only mode, New Feature: added reticle toggle New Feature: added profile management A good potion of the code has been rewritten/refac There is no working clever alchemist helper working with the current version, that is why I made this one based on a two years old broken addon, but I have zero issue take it down and enjoy it just for myself. |
|
![]() |
![]() |
Xorzoo |
View Public Profile |
Send a private message to Xorzoo |
Send email to Xorzoo |
Find More Posts by Xorzoo |
Add Xorzoo to Your Buddy List |
![]() |
|
|
https://www.esoui.com/downloads/info...Alchemist.html
-> https://www.esoui.com/downloads/info...istHelper.html I've connected your addon to the other files of the original addon, please keep an eye on that in the future so users will find addons more easily if they base on each other, or are patches of other addons. Hello Xorzoo, I just noticed your new addon is based on an existing addon. But you did not tell in the description if the author allowed you to create a new addon "with a new name", based on his addon? Did he allow you to do so? Having a GitHub repo does not automatically allow you to release the same code, even if you add fixes, under a totally new name! Check if licensing prohibits this AND if the author is okay with that. Else ask him if you can take over or if he allows to add you to the original addon's team so you can fix it officially (but keeping the original name). If you only fixed the old addon please release it with the "same name", just add "Updated" or "Fixed" behind so one can find it more easily in Minion AND release it as a patch of the original addon please (if the author enabled that at the "Other files" of that addon: ![]() -> I've connected them for you now. Else , if you have not asked the author yet, please read here: https://www.esoui.com/forums/showthread.php?t=9865 e.g. ask the author for permission to copy his addon with a new name and wait for at least a few weeks to get a response from the original authors. Thanks for respecting this, clarify this with the author and if he is okay provide me the okay from him please. If he is not okay with that please remove your addon and release it as a patch to the original addon, without changing the addon's folder and filenames, as described above! Feel free to add your name to the author tag inside the addon's txt/lua files, but keep the old devs in there too please! BR Baertram |
![]() |
![]() |
Baertram |
View Public Profile |
Send a private message to Baertram |
Send email to Baertram |
Find More Posts by Baertram |
Add Baertram to Your Buddy List |
![]() |