I’ll use the same scenario, updating test case results in QC, but if requested, I can also show how to get test steps from a test plan, or read & update defects in QC using the OTA library.
First, create a new project in Visual Studio (or Sharp Develop). It is a COM library and contains the single interface TDConnection.
If you think they're too good, or you think one of the power systems is too weak compared to the others, or you want to add a deliberate loss during conversion, just go to the config.
You can change the input and output multipliers for all four power systems individually.
These values are applied as such: output Quantity = input Quantity * input Scale / output Scale So if you had 100 MJ to convert to EU, you'd get 100 * 4375 / 1800 = 243.05 (or probably 224 in reality, due to EU pulse rules). Coal, diamond, gold, iron, lapis, redstone, tin, copper, emerald, silver, lead, uranium, and nikolite.
Non-vanilla ores only spawn if a mod that uses them exists.
Now, let’s create a connection to your Quality Center server.
You’ll need to know the URL of your QC Server and have valid login credentials with access to an existing Domain and Project.
Power systems: IC2 LV consumer: IC2 MV consumer: IC2 HV consumer: IC2 EV consumer: IC2 EV consumers have no upper limit on input pulse size, so they'll accept nonstandard wiring like Greg Tech superconductors just fine (though finding a way to output all that power might be difficult). All IC2 producers will output a single pulse per tick of their specified voltage, but this can be increased in the config. Power Converters 2.x exchange rate is based on the cost to smelt a single item in a furnace.
So today, I’m going to try to explain how the OTA API works by recreating the steps as a blog post with explanation in a simple script.