wGemCombiner explained

First rule of the wGemCombiner: don't talk about the wGemCombiner on AG.
Second rule of the wGemCombiner: the wGemCombiner is NOT gemforce.

The latter is written in C and does the heavy calculation, the former is written in C# and it's the one that executes the combines in-game.
Both are available to download for Windows at their respective Release pages.

> Sometimes, it leaves extra gems in the inventory. What am I doing wrong?
This has to be the vaguest bug report ever, when you have a reproducible issue post it here:
https://github.com/gemforce-team/wGemCombiner/issues

I'm not the one who wrote the combining algorithm (I wrote the preset recipes and part of the parsing), but I could look at it anyway.

As for which recipes to use, I recommend starting with the biggest spec you can reasonably do (I start with a single 1024s managem and I have enough mana left for everything else).
After the 1st manacycle rebuild everything with the highest spec you can and set up everything (the biggest specces are 1024s at the moment, so I don't need to rebuild the managem, but if you prefer starting with, e.g. 3 512s managems I'd rebuild them).

At that point start doing high combines while you have mana, then start using smaller and smaller ones as you go along (as I wrote in the earlier post).

It's been a while, but IIRC my routine was: 4096 x 6 - 256 - 32 - 16 - 8 - 4 - ...

Basically it removes the biggest problem recipes have, time, so you can always use the best in every case.
You can go higher than 4096, but it takes a long time and does not go on in nice multiples of 10 like 1024s/4096c.

To match the correct amps remember the -3/-4 rules or look at the corresponding omnia recipe at gemforce.

To ask further questions you might want to find another channel to discuss about it.