Player Features and Ideas Discussion

Point One:
(this might be an OCD request)
I would like to see the merger of the BPOs when it comes to items/modules which have different sizes (Small, Medium Large) but belong to the same family. These merged BPOs would gain an option in the OUTCOME box to pick the size type the player is looking for.
Type of BPOs Torrent Ammo, ABs, MWDs, Rigs and others having different size types.

Why change what isn't broken? To me it comes down to cleaning things up. By merging the small-medium-large size variant BPOs we reduce the over all number of BPOs that populate the DB and market

ABs go from 3 to 1
MWD go from 3 to 1
Hybrid ammo goes from 24 to 8
Laser crystals goes from 24 to 8
Projectile ammo goes from 24 to 8
Etc.

The price change to buying these new BPO bundles should fall in between the current medium and large price points.
Does this effect me? Yes and no, as my core character build is as an industrial toon I already own the different size module BPOs (in some cases I own multiples of the same BPO). What this does for me is gives more more function from BPs I already own.

Does it hurt the new bro with higher introduction cost: I say no, as they already start with 500k SP. they got basically got a 2 week head start compared to when I made this toon when it comes to SP.

Point Two:
Merge the modules which have similar function (Sensor Arrays, and Sensor Boosters) and create a new item type that can be placed in ether low or medium slots. With the effect/stats of the module changing depending on where it is placed.
Why? I feel that merging these modules and providing alternate stats/effect depending on the placement of the module could simplify some things.

If you are not aware, March is a major teiricide for modules. CCP is merging ECCM and Sensor modules together. I believe the ECCM and Sensor thread alone talks about removing nearly 100 modules from the game.

What this idea does is this: You take something like the Sensor Booster and Sensor Array, each has say 10 variants. Make a new module that has different PG/CPU and differing effects/stats depending on what slot it is in. This takes 20 modules types down to 10.
Give this same treatment to Tracking Computers/Enhancers, Omnidirectional Computers/Enhancers, Missile Guidance Computers/Enhancers. If each group has 10 modules, that makes a total of 60 modules (80 if you count our sensor modules) and takes that down to 30 (40 including our already counted sensor modules) modules.
That is 40 fewer items to populate in the market.
40 fewer items to clutter our hangers
40 fewer items to sit in rat loot tables
etc.

Point Three:
http://community.eveonline.com/news/dev-blogs/eve-online-sso-and-what-you-need-to-know/

For important reasons, I have linked the SSO dev blog.
What I want to request is this! I would like for CCP to add in the ability to control the start, stop, complete functions of the industrial window, so that they can be used through 3rd party apps.

As I am a fan and user of the iOS App Neocom, I decided to check something.
A few patches back, CCP added the means for players to pull and push ship fittings via the API and SSO. I started up NEOCOM, went to the fittings and tapped "browse in game fits" from there I logged in. And could see my saved fits. It was really nice.
Now take that function and give industry like manner treatment.

Now, from my understanding, a website/application that wants to use the SSO has to adhere to CCP and be registered so they can receive the certificate.
By making these industrial API calls only work when connected via SSO they add a means to counter bots.
If the CCP security team checks these applications from time to time or have players report them, they can see if the appicstion/website provides any "automation" which would be a violation of the SSO agreement, thus killing the certificate for that site/application and preventing bots. CCP can then go and do more to punish people who used the app/site and the developer.

The issue isn't if people will bot, we know there are people who do. What matters is, can there be a security function put into place that chops off the offenders heads.

TL:DR
Reduce item DB/Market Items by merging modules/ammo of different sizes into a single BPO with the ability to select which size in the OUTCOME.

Reduce the number of modules by merging the types that have medium slot modules and low slot. E.g. Sensor boosters and sensor arrays

Provide API backed by SSO security calls that allow control over the industrial processes.

So if i just want to make small afterburners, i have to buy the obviously more expensive bpo that builds them all?

At the other end of that spectrum is the new player killing a single rat and getting a few thousand ISK.
So new player want to start small in their industrial adventures now has to work roughly 7.8 times as long to buy into that first PO. And yet as you point out older characters effectively see no change in how long it takes them to earn the ISK to buy your new and improved BPO. Sounds like a terrible idea to me so I say

-1

Point 1:
Why? As in what purpose does this serve?

As of right now, I can make the 3 sizes at the same time, because I have three different BP's. In your proposal, I would be slowed down quite a bit, unless I wasted oodles of ISK and time making BPC's first.

Point 2:
I think this would actually cause more confusion than it might alleviate.

Point 3:
Already asked, but I'll echo it: How does this stop/hinder botting?

Gadget

It doesn't work that way. The engines on this are not simply scaled up versions of the engines on this. While mechanically similar, they use completely different components, and usually completely different materials.

Secondly, while this suggestion would decrease the number of item entries in the database, it would also increase the complexity of the database, while doing very little to decrease the overall size. The size of a database is not the number of entries, but the data in the various fields of those entries. This data would not magically go away, but would simply migrate into new fields.


Those items have similar function, not identical function. Again, you don't seem to understand how databases actually work. The data within each entry doesn't go away. You're also overlooking the fact that Sensor Boosters and Signal Amplifiers don't actually perform identically SeBos are active modules, provide more scan res bonus than SigAmps, and can be scripted. SigAmps provide additional targets, have reduced scan res bonus, are passive modules, and cannot be scripted. There's just no way to merge those two modules without a total rewrite of the database, and possibly core coding.


So, you want to try to stop bots by giving them even more tools to bot with? How does this even make sense to you? There's already numerous third party applications that have triggered events based on data provided by APIs. The only thing that keeps these third party apps from becoming bots is the inability to effect the game without being logged in. Your suggestion breaks this, thus further enabling bots.

Point 1: Lets see - buy more than one BPO.

Point 2: Not really - low slot = passive. medium = active. You reduce a lot of these has a med slot version that does this, or does that with a script. or a low slot just is just passive.

Point 3: How do you stop bots? The hope is that by using the SSO, and this prevents people from taking all their corp mates production/research slots. Will it prevents bots, it hard to say. If there was a way to limit to only having one SSO login from an application at a time. it would mean the bot has to log on, do the job. and then log off to log into the next.

And all I want is BPC's to become stackable...

I remember a CEO of an industrial corp wrote a very long post on this topic.
Basically if you sum his post, it comes down to:
- EVE doesn't have a good way to let mining ops work well to be managed by 1 person;
- EVE doesn't have a way to manage collective production, provide security, split income etc;
- being an indy corp CEO is extremely frustrating and unrewarding activity.

This is funny, because your understanding of the tech involved is roughly on par with the Amish.

Disliking your particular suggestions and disliking change are entirely different things. Conflating them is profoundly ignorant.



Explain how anyone is going to check an application that is only accessible at ::1.

There is absolutely no way they are going to allow API writes to gameplay systems. They allow it for ship fittings and contacts because that is strictly a convenience, and offers no benefit without logging in via the Eve client.

Disallowing API writes IS the security function.




Did you actually read the reasoning behind that change?

It's 100% gameplay reasons. ECCM as a standalone module offers poor value: If you don't encounter ECM (or aren't doing some probe-resistance shenanigans), it does very little for you.

It has nothing to do with item count reduction, which seems to be your sole concern for some nebulous reason.