EVE Information Portal

Small typo in the devblog:

There are no practical plans for any of this - but there could be cases where if you want to query endpoints that cost us lots of bandwidth to deliver a lot, we'd ask you to pay for that. But we have no such end points today, and no such setup planned. I just wanted to flag that there is no guarantee that all access will be free for ever - just trying to manage expectations, in case we run into something that is too expensive for us to deliver for free, but that we could keep if developers were willing to pay.

/Seagull

SDE, access to the current API, and all other dev resources will be freely available, and not require the Dev License. Only CREST usage and Single Sign On usage will require the license.

I'm so excited to hear about CREST Beta. Fan apps like Aura are going to have a field day with this and I can't wait to see what they come up with.

Big ups to CCP to taking them to really sit down, look over the 3rd party developer license and bring out something which is a true boon to the community. I don't just mean from a free aspect though that is part of it. The risk involved with a move like this is tremendous and I'm so happy to see CCP Games is sticking with their tag of being Fearless in a way that is positive for the game and the community.

Happy coding to all!

they did not, 4.1 is the only mention of payment, and basically it doesn't specify in-game itself, actually it might imply it,
but its not clear, i'm not an US-Law professional.
hence i'm asking.

ok, before i get into rage about a simple request for clarification that i made and how people white knight in about it, i'll just stop it here.
The License does not mention ingame payments in any way, nor does it imply such intent. The Blog is unclear in the wording about it, and could imply it is not allowed. the part you quoted sais "charging" and avoids to differenciate between a real charge, and the transfer of ingame currency which legally and technically is owned by ccp anyways.

Now i'm dealing here with a license that is put under the law of a country which is known for its interpretable law, and cofusing law system.

So please forgive me when i'm trying to find out in very clear and reliable words whats meant.

Oh i wasnt trying to give you a hard time about anything, I was just relating what the dev said on the matter of charging ISK, vice donations. I skimmed the licence agreement, but thats about it.

The access to the source code is a show stopper. Unless CCP is willing to sign a NDA and licensing agreement with me.

• You can take ISK donations and Real Money donations to cover your costs, but you can't charge outright for usage, access or download of your application.
• You can show ads in your application, but they can't be ads for stuff that's EULA-breaking, like RMT ads. We also reserve the right to ban other types of ads at our discretion - but this is a right we need to retain to protect our business, not intended to be an arbitrary or draconian ad policy. We just need the ability to deal with this on a case-by-case basis.

Why out-right ban this?

Until these rules change - I don't see anyone other than an student, coding enthusiasts, and starving artists/people with no business sense building apps for EVE with CREST. As anyone who has the skill and grit to build something valuable needs to invest a lot of time and energy into building and upkeeping a 3rd party app. Someone in that position will probably have a family/mortgage to worry about - so therefor wont invest in your ecosystem.

So why can't we profit from our efforts?

After going back an re-reading the post/licence agreement, I can see how it could be confusing. I was just assuming the monthly fee for the KB was in ISK, but it does not clearly state that fact. So the ISK for usage thing is still grey, although I likely suspect that as it is currently written, we will not be allowed to charge ISK for our services developed w/ the CREST API.

With regard to the souce code, if I release something that is opensourced I dont think would be a problem, however if I intend to keep it closed source, then there might be an issue there.