View Entry Info: Companion API stopped having Engineering Data

PC/MAC Bug Reports
Page 1 of 14 1234511 ... LastLast
Results 1 to 15 of 201

Click here to go to the first staff post in this thread.
Thread: Companion API stopped having Engineering Data

  1. #1

    Companion API stopped having Engineering Data


    All the time(100%)

    Time of occurrence

    Date of occurrence

    None / N/A



    Ship Type

    Commander Name

    I'm told by the EDMC developers that the companion API used to extract player ship information is no longer outputting engineering modifications as it used to.

    1. It's not "secret data" all the information is in the outfitting screens
    2. People are going to put that information into websites anyway.
    The question is... how long will it take them 5 seconds or 5-15 minutes.

    I would urge you to reconsider the option to remove it and put it back in because all you're doing is putting a knife in the toes of your community.

    Steps to Reproduce

    Additional files?
    Still a problem in 2.3.01

  2. #2
    Yeah, as someone that uses EDMC / Coriolis for my ship builds - veeeeeery useful to not have to play data entry every time I get a new ship / mod.

  3. #3
    This is quite bad change , it was very useful and often used. Hope it's only glitch and not purposely removed.

  4. #4
    I'm just hoping that this was an oversight due to not testing 2.3 against the companion API until it went live. Please fix this (given apparently the designers told hchalkley not to put this modifications information into the outfitting journal events, which seems strange unless it's different from what we had in the companion API).

    To be clear, without this people have to tediously hand-type in all their engineer module values into sites like Coriolis. It was great to just be able to click in EDMC or EDDI and get a full import of the ship into

  5. #5
    at new companion api cut modules information from non actinve ships. its very bad

  6. #6
    Argeed! Bad decision, bring it back!

  7. #7
    This is a giant step backwards for everybody who uses the headline feature engineering, please undo this change.

  8. #8
    Huge crapolio. Please revert this change.

  9. Click here to go to the next staff post in this thread. #9
    Hey Cmdrs,

    Thanks for the reports.

    I've passed this on to get checked out.

  10. #10
    Add me to the list of people who find this feature incredibly useful and would be pretty annoyed at having it removed.

  11. #11
    +1 to those that were very sad to see this, and hoping it was unintentional and fixable!

  12. #12
    Please Bring this back thanks. Love the game!

  13. #13
    One step forward, three steps back. Please add me to the list of commanders who are seriously unhappy about this.

  14. #14
    Dont care if it gets fixed in the journal or the API - so long as the EDMC can pick it up.

  15. #15

    Please bring it back FDev!

    Big surprise today after updating EDMC, this is a step backwards in integration with the Elite Developer Community, we need this data to be easily accessible, especially since this was in the game before. Please bring it back

    CMDR Faranhor | Dark Echo

Page 1 of 14 1234511 ... LastLast