Wrong CEP version on GitHub

It is 3.13, they just forgot to change the version number in game. Confused the heck out of me too at first but when I went in and played an actual game it is defiantly 3.13 (changes to the tech tree are pretty obvious).
 
Cheers for that. Seems the gatling gun still has its 1 iron resource requirement which got me confused when I looked at it quickly!
 
Somehow the gun unit resource requirement wasn't nixed (MG and Bazooka still require oil too). It's easy to take out in the meantime.

They're also listed both as combat class melee and combat class recon.

Other "bug" notes: I think the added units (missile destroyer, bireme) would need their cost adjusted to the 2x scale, with an added 20% cost.

The unit upgrade cost is set at 1.5x instead of 2x.
Infantry still has a unit AI reference to paradrops from several versions ago.
Both Airborne and XCOM are listed as vanguard style units still. Intended?
There's an upgrade path for ships still in the start file alongside the upgrades file (redundant/overriding).
I don't see a change for walls to be 25% from 0. That list, part of it at least, is still in both the start and end sql files too (redundant/overriding).
Bazooka doesn't get a ranged defence bonus ala gatling gun and machine gun.

Aqueducts were nerfed to 30% from 40%, not documented?

I don't actually see the change to hand-axe (will check the interface/tools directories). - found it.

Carriers are still listed in that upgrades file to upgrade to missile destroyers and from destroyers (intended?, seems like a bad idea)
 
Ive got a fix for Gatling guns/MG/Bazooka resource requirements, walls conquest prob and unit upgrades on the way.

Every time I try to sync the files in Github I get an error message saying "'Failed to sync this branch' though. I'm a real newb at Github and don't know what I'm doing wrong,

\Skodkim
 
There should(?) be an error message with more information but from what I remember, the most common error is that you're out of sync with the branch. You have to pull all the latest changes before you can push your own changes to the branch.
 
There should(?) be an error message with more information but from what I remember, the most common error is that you're out of sync with the branch. You have to pull all the latest changes before you can push your own changes to the branch.

Got it working this morning. Have to say I'm still not comfortable with using it though :mischief:

Edit: How do I make sure that I pull all the latest changes and Work on the right branch (yes, I'm really not sure about that ;-) )

\Skodkim
 
Edit: How do I make sure that I pull all the latest changes and Work on the right branch (yes, I'm really not sure about that ;-) )

Honestly, I have no idea. I don't have too much experience using a VCS too.

I was totally useless using GitHub on a separate branch myself. I mostly relayed any bug fixes to Expired until Thal made me a repo collaborator which let me push fixes directly. You should try contacting Expired for help with GitHub commands or Thal about becoming a repo collaborator.
 
to keep your fork up to date (given you have your own clone):
git pull https://github.com/Thalassicus/cep-bnw.git stable
this should fetch latest changes from the "stable" branch and merge them with you clone

show all branches in your clone (starred one is your current working branch):
git branch

to make sure you are on the proper branch in the (in this case the original repo):
git checkout stable

if you are working on a different branch (e.g. new-features) and want to merge changes from master you can use
git rebase stable


Edit: Doing that with linux though, I have no idea how fancy windoze GUI's work :) I would recommend using some kind of console with win too, though.
 
You can bring up a Linux console using the GitHub for Windows app. Those commands should be very helpful.
 
Top Bottom