Advice for choosing the compilation way

[Meridian]

Now I will try to fork but no sure what. OXC or extended? Not sure. My aim is to include more advanced options that already implemented by community but never used, like advanced scanner, throw trajectory, manual control of civilians and etc. So you will get tons of experimental user decide options.

You can only fork OXC... you cannot fork Extended, because it is already a fork... thanks Github.

Anyway, fork whatever YOU want... people will either like it or not. Btw. I will be looking at throw trajectory and motion scanner in oxce+ too, soon.

[DoxaLogos (JG)]

You can only fork OXC... you cannot fork Extended, because it is already a fork... thanks Github.

Actually, I think you can "fork", but it's using git itself to implement it by adding remote repos.  It's outside of Github for adding another fork of the same repo.  I did this while working on Shoe's fork before it was merged upstream.  I had forked OXC and then added his fork as a another remote repo to my fork and pulled it into a branch.

[Xtendo-com]

Thanks, I will try to learn git features before implementing anything else. My unoriginal nickname was already taked in github, so I changed my nickname to someone else.

[Xtendo-com]

I will be looking at throw trajectory and motion scanner in oxce+ too, soon.

motion scanner easy to include using this diff but not easy to fix issue that spoil a level since it uses a render code that checks title by title, level by level "if current title contain unit" and "if unit is scanned in that turn", so I'm trying to found a way to manually change level to lowest for rendering scan result in battlescape.

Fixed, but spends more not necessary cycles.