Corporation Projects & Freelance Jobs Improvements

Council Of Stellar Management Assembly Hall
1

I returned to New Eden last November after a long AFK period and started using Corporation Projects and Freelance Jobs heavily. For small/medium corporations, this is a major management breakthrough! it enables in-client automation for rewards, SRP/compensation, and activity tracking without relying on third‑party websites or bots.

After several months of day-to-day use, I’d like to suggest a set of incremental improvements (mostly “patching gaps” in the existing system rather than major redesigns):

  1. Add “negative/exclusion” filters (ACL-style blacklist logic)
    Allow projects/jobs to not only include filters, but also exclude specific:

ship types/hulls,
regions/constellations/systems,
organizations (corp/alliance etc., based on existing available dimensions).
Why:
AOE ships in PvE can generate friendly-fire PvP damage and unintentionally trigger PvP reward rules. Some hulls (e.g., Ishtar) are too PvE-common to be valid SRP hulls for PvP, but without exclusions we must split rules into many separate projects. Roaming/harvesting teams often need “kills outside home space” rules—being able to exclude home space would reduce duplication significantly.

  1. Increase selection limits for filter parameters (10 is too low)
    Raise the cap by several times. Real corp policies require larger whitelists/blacklists (approved hull lists, operational areas, etc.). The current cap forces unnecessary project fragmentation.

  2. Insurance/SRP option to exclude cargo / ship hangar contents
    Add toggles so payouts can be calculated with options like:

hull + fit only,
exclude cargo,
exclude ship hangar contents.
This prevents payout inflation and reduces abuse/arbitrage risk.

  1. Fix missing/incorrect hull valuation on some killmails (hurts insurance)
    Some hulls (Triglavian ships, capitals, etc.) have missing/incorrect valuations for long periods, which weakens project-based insurance/SRP and forces manual handling or separate projects.

  2. On project closure/deletion, return remaining funds to a specified corp wallet
    Instead of always returning to the master wallet, allow returning to:

the originally selected funding wallet, or
a wallet chosen by the project manager.
This supports budgeting and reduces accounting overhead.

  1. Allow editing existing projects/jobs (instead of copy/recreate)
    Support direct editing (or a versioned “edit and publish” workflow). Today’s copy/recreate/retire process is too heavy for iterative policy changes.

  2. If Freelance Jobs are meant to replace/cover corp-project functionality, increase job capacity limits
    If CCP prefers Freelance Jobs for stronger ISK sinks and structured participation, please significantly raise:

how many jobs a member can accept simultaneously,
location/availability constraints.
As an example, I already need ~46 projects just for basic rewards/SRP/ADM incentives; if those must become Freelance Jobs under current limits, it’s not feasible.

These changes reduce reliance on external tooling and lower the learning/operations burden for small corps, letting players focus on gameplay rather than manual bookkeeping.

2 Likes