Page 3 of 15 FirstFirst
1
2
3
4
5
13
... LastLast
  1. #41

    Re: New UI Add-On Development Policy

    Quote Originally Posted by bluspacecow
    No it isn't

    The key part of that paragraph you linked is that you can not charge people to download or access an addon.

    The new curse client's premium service is when it's installing it. In no way shape or form does it prevent you from downloading or acessing an addon it just takes a little longer thats all.
    It clearly states that you cannot charge for services related to the add on. The curse downloader is an add on related service. As I said, its vague enough that Blizzard could certainly go after them.

  2. #42

    Re: New UI Add-On Development Policy

    Quote Originally Posted by K21Nova
    ...providing an add-on faster, or easier, is a service related to the add-on. Hence, Blizzard does not like.
    I think the spirit is they don't like charging to download the addon prevent you from downloading an addon.

    Let's look at that policy again shall we ?

    All add-ons must be distributed free of charge. Developers may not create "premium" versions of add-ons with additional for-pay features, charge money to download an add-on, charge for services related to the add-on, or otherwise require some form of monetary compensation to download or access an add-on.
    Distributed free of charge ?

    Check!

    Addons with additional for pay features ?

    None !

    Charge money to download an addon ?

    Nope not charging for people to click a button to download the addon

    Charge for services related to the addon ?

    Yeah this will need some clarification. Especially since technically this could cover advertisements on addon sites . Will this mean addon sites will now have to close ?. Don't worry tho Kaelten's asking Blizzard for some clarification

    otherwise require some form of monetary compensation to download or access an add-on?

    Nope. They're not charging people to click a button to download an addon. It's just more buttons so hence takes longer.

    IMHO i don't see anything in there about make it slower or harder to download an addon being bad.

  3. #43

    Re: New UI Add-On Development Policy

    Quote Originally Posted by nazrakin
    It clearly states that you cannot charge for services related to the add on. The curse downloader is an add on related service. As I said, its vague enough that Blizzard could certainly go after them.
    Which is exactly why Kaelten's asking Blizzard for a little clarification.

    Because it's vauge enough to also include page advertisements on addon sites.

  4. #44

    Re: New UI Add-On Development Policy

    So does this mean that Zygor can no longer charge for his in-game leveling guide add-on?

  5. #45

    Re: New UI Add-On Development Policy

    1) Add-ons must be free of charge.
    All add-ons must be distributed free of charge. Developers may not create "premium" versions of add-ons with additional for-pay features, charge money to download an add-on, charge for services related to the add-on, or otherwise require some form of monetary compensation to download or access an add-on.
    that's a bitch move blizz. although my addon is free of charge knowing i can't, one day, if i wanted, charge for something I worked hard on is kinda bullshit.

    2) Add-on code must be completely visible.
    The programming code of an add-on must in no way be hidden or obfuscated, and must be freely accessible to and viewable by the general public.
    Why? So they can make sure it contains no malicious coding? Because we've had so many problems with people getting keylogged by actually lua files, right?
    3) Add-ons must not negatively impact World of Warcraft realms or other players.
    Add-ons will perform no function which, in Blizzard Entertainment's sole discretion, negatively impacts the performance of the World of Warcraft realms or otherwise negatively affects the game for other players. For example, this includes but is not limited to excessive use of the chat system, unnecessary loading from the hard disk, and slow frame rates.
    good rule. I support it to the fullest.

    4) Add-ons may not include advertisements.
    Add-ons may not be used to advertise any goods or services.
    I support this too. Ads have no place in this game.

    5) Add-ons may not solicit donations.
    Add-ons may not include requests for donations. We recognize the immense amount of effort and resources that go into developing an add-on; however, such requests should be limited to the add-on website or distribution site and should not appear in the game.
    I recognize donation requests in addons are fine as long as they aren't annoying. If they are limited to a small pertain of the main box i don't see the problem but i'll let this one slide.

    6) Add-ons must not contain offensive or objectionable material.
    World of Warcraft has been given a "T" by the ESRB, and similar ratings from other ratings boards around the world. Blizzard Entertainment requires that add-ons not include any material that would not be allowed under these ratings.
    Good rule.

    7) Add-ons must abide by World of Warcraft ToU and EULA.
    All add-ons must follow the World of Warcraft Terms of Use and the World of Warcraft End User License Agreement.
    Wait I can make addons that are against the ToU and EULA? Since when? Sounds like this one is just to cover your own butt if something goes wrong.

    8 ) Blizzard Entertainment has the right to disable add-on functionality as it sees fit.
    To maintain the integrity World of Warcraft and ensure the best possible gaming experience for our players, Blizzard Entertainment reserves the right to disable any add-on functionality within World of Warcraft at its sole discretion.
    Didn't they do this already?

  6. #46

    Re: New UI Add-On Development Policy

    So does that mean that I can sue Blizzard for all the stealing of my intellectual properties now as everyone who likes my addons steals the code and adds it to their UIs?

    With the 'wide open' concept, all the code is there ready for anyone to do with as they wish. Even stuff, that I've written and have ownership of.


    PS..No I don't have addons but just throwing this out there as everyone is bringing up the looseness of the language of the agreements.

    Personally I see nothing wrong with Carbonite. Sure yes I can download 15 different addons and almost do the same thing, but none of those addons are updated a few times a month if any. It makes the game more enjoyable knowing that my addon 'suite' is going to work when I log in and if it suddenly gets broken, in a day if that it will be fixed. Now with this development policy, blizzard is saying that you cant hold ownership on any code you write for an addon, and everything becomes public domain..Umm, sorry that isnt right.

  7. #47
    I am Murloc!
    Join Date
    Mar 2008
    Posts
    5,275

    Re: New UI Add-On Development Policy

    Quote Originally Posted by Meebo
    It's just a shame that this doesn't effect addon downloaders like Curse-Updater.
    If you ask Kaelten, I'm sure he disagree. Opposite to common belief, bandwidth is not free.

    What Blizzard is trying to prevent is major add-on authors like Carbonite to profit on add-ons.

    And to bring more developers in though the "open source" spirit, by banning obfuscated code.

  8. #48

    Re: New UI Add-On Development Policy

    Quote Originally Posted by chrisminis
    I was just wondering how they are gonna disable the addon usage?

    Are they gonna recode the game, so addon becomes unuseable? Unlikely.

    My thought? bullshit.

    How are they gonna remove already existing addons usage in the game?

    But i understand that they dont want "donate please" and Ads around addons.
    They've done your first suggestion before when they removed the ability for a script to act in your stead without a button click, such as autocleansing, and they can do it again.

    If they can't do so without breaking something that they want to keep in the game functionality, then they can just as easily announce that, due to noncompliance with the rules, the use of X addon is now a bannable offense, and since they know exactly what addons you use, they can easily track down those who are using them.

  9. #49
    I am Murloc!
    Join Date
    Mar 2008
    Posts
    5,275

    Re: New UI Add-On Development Policy

    Quote Originally Posted by theKarn
    that's a bitch move blizz. although my addon is free of charge knowing i can't, one day, if i wanted, charge for something I worked hard on is kinda bullshit.
    In the end of the day, are you writing add-ons for money or for fun? Nobody say you have to distribute your add-ons. And if you do, is it not for the love of the community?

    Quote Originally Posted by theKarn
    Why? So they can make sure it contains no malicious coding? Because we've had so many problems with people getting keylogged by actually lua files, right?
    No, so others can maintain and renew otherwise obsolete/abandoned code. And to help new authors learn from other add-ons.

    This is in the heart of almost every programmer who ever released a piece of open-source work. It's part of the programmer community. But I sense you're not part of that?

    Quote Originally Posted by theKarn
    I recognize donation requests in addons are fine as long as they aren't annoying. If they are limited to a small pertain of the main box i don't see the problem but i'll let this one slide.
    Authors should keep donation requests to their website and the source code.

    The rule is only about visual content. You're free to advertise your website and ask for donations in the source code.

    Quote Originally Posted by theKarn
    Wait I can make addons that are against the ToU and EULA? Since when? Sounds like this one is just to cover your own butt if something goes wrong.
    You didn't play in WoW:Classic I can guess. Cosmos had issues that was close to breaking the ToU several times.

    There have also been developed a add-on that changed the GM Help Frame with help of a separate application and some memory hooks. Which allowed in-game browsing. That's clearly against the rules.

    It's mostly to cover their own ass, yes, as the current 'de facto rules' are: "if it's doable with the available API, it's legit".

    Quote Originally Posted by theKarn
    Didn't they do this already?
    The last paragraph is just a legal statement. It's not relevant for regular users.

  10. #50

    Re: New UI Add-On Development Policy


    In the end of the day, are you writing add-ons for money or for fun? Nobody say you have to distribute your add-ons. And if you do, is it not for the love of the community?
    I code because I love coding. :P

    No, so others can maintain and renew otherwise obsolete/abandoned code. And to help new authors learn from other add-ons.

    This is in the heart of almost every programmer who ever released a piece of open-source work. It's part of the programmer community. But I sense you're not part of that?
    Meh, You have a point I guess but why should this be a rule?

    I'm part of the I do what I love community lol

    Authors should keep donation requests to their website and the source code.

    The rule is only about visual content. You're free to advertise your website and ask for donations in the source code.
    putting your website in your addon could be considered advertising.

    You didn't play in WoW:Classic I can guess. Cosmos had issues that was close to breaking the ToU several times.

    There have also been developed a add-on that changed the GM Help Frame with help of a separate application and some memory hooks. Which allowed in-game browsing. That's clearly against the rules.

    It's mostly to cover their own ass, yes, as the current 'de facto rules' are: "if it's doable with the available API, it's legit".
    I started in 1.10. Cosmos came CLOSE to breaking the ToU, but they never truely broke it. W/e they did was surely fixed quickly along with decurse/cleanse being put on the GCD to fix that addon exploit.

    The last paragraph is just a legal statement. It's not relevant for regular users.
    No, it means they can deny use of any addon, helpful or not, depending on how they feel that day. I know blizzard has only went after things that have a negitive impact of the game but who's to say the will not go after Bartender because it modifies the visual experiance of the game?

  11. #51

    Re: New UI Add-On Development Policy

    Quote Originally Posted by theKarn
    that's a bitch move blizz. although my addon is free of charge knowing i can't, one day, if i wanted, charge for something I worked hard on is kinda bullshit.
    I get where you are coming from, but I believe that is why Blizzard said nothing about people taking donations still.

    In the sense of charging for people to use your add-on(i know yours is free, saying it for general purposes) then you would be making money off their program. Yeah you wrote the code for the add on, but without the game, add-ons dont really amount to much.

  12. #52

    Re: New UI Add-On Development Policy

    Regarding any supposed intellectual property for addon developers I think one major point is being overlooked. That is that any addon that does anything remotely worthwhile must make use of the wow api library (owned by blizzard), and by making use of that in an addon you implicitly agree to to their terms.
    It's more than simply saing an addon needs wow to exist in, an addon is literely built out of components blizzard created and provided. Top to bottom blizzard holds all the cards where addons are involved.

  13. #53

    Re: New UI Add-On Development Policy

    Quote Originally Posted by alt
    You obviously have no idea of the concept of intellectual property. Simply put, companies take a dim view of other people making money off their intellectual property. It can and will erode their copyright protections and brand image. Addons are not different from books, cards, movies, etc. in this regard.
    While, I like the idea of all add-ons beings free... I think this kinda sucks. I mean what's the difference between an add-on that enhances the features and user experience of a game versus something like McAfee anti-virus for Windows or RegCleaner? These softwares don't work independently from Windows, they enhance the user experience of Windows.

    Of course Microsoft allows software development like this for their product, whereas Blizzard doesn't.

    Anyway, maybe Blizzard needs to host their own addons site, put up ads, and share profits with the developers like Google shares profits with YouTube contributors.

    Additionally, it would help Blizzard's image if when they blatently copy and integrate an addon into the game themselves that they reward the developer in some way... maybe through a monthly addon contest with a cash prize.

  14. #54

    Re: New UI Add-On Development Policy

    Quote Originally Posted by calico0
    Regarding any supposed intellectual property for addon developers I think one major point is being overlooked. That is that any addon that does anything remotely worthwhile must make use of the wow api library (owned by blizzard), and by making use of that in an addon you implicitly agree to to their terms.
    It's more than simply saing an addon needs wow to exist in, an addon is literely built out of components blizzard created and provided. Top to bottom blizzard holds all the cards where addons are involved.
    wait wait. so you're saying blizzard owns my addon? That's something I'm not willing to accept.

  15. #55

    Re: New UI Add-On Development Policy

    Quote Originally Posted by theKarn
    wait wait. so you're saying blizzard owns my addon? That's something I'm not willing to accept.
    Think of it this way:

    The Blizzard UI API is a bunch of Chimps, each capable of doing certain things when told how to.
    You are a Chimp Trainer, capable of telling the Chimps what you want done.

    You can write whatever kind of cool and unique scenarios (addons) you want to get those Chimps to jump through their hoops, or balance balls on their heads, or throw feces at gold farmers, but at the end of the day, BLIZZARD OWNS THE CHIMPS, and you are considered to have entered into an agreement with them in order to have been allowed access to knowledge of what instructions those Chimps will follow.

    Your scripted scenarios are yours, but they are still useless without the Chimps, and BLIZZARD OWNS THE CHIMPS.

  16. #56

    Re: New UI Add-On Development Policy

    Quote Originally Posted by theKarn
    wait wait. so you're saying blizzard owns my addon? That's something I'm not willing to accept.
    You are welcome to remove all of blizzard api from your addon, you should own what is left. Naturaly it would become about as useful as a mesh umbrella.

  17. #57

    Re: New UI Add-On Development Policy

    Wtf??? u had to pay for carbonite, for zygor, for x addon that required payment?.... come on... this is internet, if i like the stuff i might buy it if not... /shoo:P :<


    Wait I can make addons that are against the ToU and EULA? Since when? Sounds like this one is just to cover your own butt if something goes wrong.
    Yes u can make a bot to... actualy atm u can use an injection tool that will remove all lua limitations and u can(not limited to) bot easy with an addon (even better then in classic wow eh? :P ), yes this is illegal but... fish bots/glider/etc

  18. #58

    Re: New UI Add-On Development Policy

    Quote Originally Posted by Keldin
    Actually the Add-On is also theirs the moment its designed to hook onto the WoW .lua code.
    You are very much incorrect. Interfacing with an API does *not* transfer intellectual property rights. It's quite the opposite, it grants an implied license.

    The difference is that before this announcement, there were no restrictions on that license. Now there are. They won't ever own the code, but they can take action against you if you operate outside of their licensing rules.

  19. #59

    Re: New UI Add-On Development Policy

    Quote Originally Posted by drakonblayde
    You are very much incorrect. Interfacing with an API does *not* transfer intellectual property rights. It's quite the opposite, it grants an implied license.

    The difference is that before this announcement, there were no restrictions on that license. Now there are. They won't ever own the code, but they can take action against you if you operate outside of their licensing rules.
    See that's what I thought. Hell blizzard doesn't even technically own LUA in the first place. they are using it under the MIT licensing agreement.

  20. #60

    Re: New UI Add-On Development Policy

    Quote Originally Posted by theKarn
    See that's what I thought. Hell blizzard doesn't even technically own LUA in the first place. they are using it under the MIT licensing agreement.
    They own their specific implimentation of LUA I suspect.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •