Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Win64

The WORST "feature"!!! I was really hoping that my custom settings would be in the game directory - NOT ON MY JAMMED UP C DRIVE. Is there a way to configure this for another directory - like a subdirectory off the GAME directory.  I regularly backup my games directory to the cloud (not on my C Drive). It just sucks that you did this! Now I have to setup a script to copy from my C to my D to make backups quick and easy. I rarely  backup my C Drive (OS) because I don't keep DATA on the C Drive. For the same reason, I do backup my other drives frequently and often because they contain volatile data. I really don't play on the laptop.  

Other than that, everything is so tedious and everything seems to be so manually oriented for configuration. Little or no usable documentation on  what all these parameters and such mean in the Unit DB. Where is it stored. It would take me days to create new UNIT NAME FILES, for instance. I was really hoping for an easy way to import my unit names files! Sadly, none that I have discovered. The GE file XML is corrupt and won't load in my XML editor.

I was really hoping to be able to import my custom unit database(s) and names files from EDEE as a starting point in EDCE - Apparently I cannot. I have configured so many great features in the unit databases in EDEE like Subs can't deep submerge in coastal waters or can't enter coastal waters while deep submerged, I added an air superiority fighter which is great for Air to Air but not great for attacking ground targets. I also added a special "wild weasel" aircraft that suppresses anti-aircraft fire (very highly resistant to Air-to-Air and Ground to Air fire) for the rest of the air attack to follow. Ships should have to refuel like planes but on a much longer time scale. My aircraft carriers are Nuclear so literally no refueling. I replaced the Patrol boat with a Guided Missile Cruiser that can carry and launch 2 short range missiles. I made my satellites have a very wide detection range (just like satellites do on Earth). I permitted my A/C to carry Helicopters, Fighters, Air Superiority Fighters, Wild Weasels. My submarines can carry 2 missiles and can launch while surfaced or submerged but not deep dive. My bombers can carry 1 short range missile.  My Carriers and my Submarines can move faster than my Cruisers, Battleships and Destroyers. My trucks can carry and launch 1 missile. All ground units have been given a range (large) but it requires they enter a city or port periodically to replenish supplies and fuel. For instance, the range on Armor set so that every 12 turns they need to enter a city or port or be  transported. The range on a Battleship is similarly set. In real life, ships all must replenish and refuel - even nuclear powered. Nuclear powered AC and CR and Submarines. For nuclear powered ships, it is every 40 turns. Another change is that all ships can only go at half speed in coastal waters. All of these updates more clearly simulate today's military environment.    

Haven't gotten around to playing a game yet.  I am not particularly impressed with the difficulty imposed by XML for editing name files and such without the facility to cut and paste lists of names of units into those files. 

Regarding the drive issues, this location is initially determined by the Unity Engine and that is pretty standard. Being a tech weenie I personally do not like the choice, but it is what it is. However, you can override it.  Check the manual, which is online as well: 

http://killerbeesoftware.com/edce/code/manual/EDCE.pdf

and around page 93 look for "Changing The Game Data Location".  Also make sure you know the difference between the "Game Reference Directory" (where you put the game) and the  "Game Data Directory" (which is what you  want to move).

In regards, to portability of the unit databases from EDEE, that is not possible at this time.  EDEE is different, and there are actually more features in an EDEE DB than in an EDCE. The development of the features of EDEE's DBs was a process over the 15 years of the game's life, with numerous change requests and added patience. For EDCE, we have to start that process somewhere, and here we are. 

I would say that if you have a DB you used often for EDEE, build an EDCE DB as you did the former, which is one unit at a time over time. If there is a feature that appears missing, let me know and it can be discussed. But in terms of Unit DBs from EDEE into EDCE, there is no conversion path except you seeing what works and what doesn't, and it is possible that only EDEE will work the way you want it to.

Regarding Unit Modification in general, this is an extra part of the game program and not the game itself. If someone's perspective is modification is the game, then I can see the disappointment. Hopefully over time I hope it will develop more, but at the moment it is in fact quite bare bones. I have made several posts over time that there is only so much that one developer can do, and rather than not have this feature because it cannot be perfect for everyone, I have exposed it so that people that want to take the extra effort can modify the game.  But like augmenting the source code, or creating graphics, there is a level of effort needed to undertake to make those changes. If anyone does not have the patience  for that, I would recommend not trying to make modifications, as I can see it would be an exercise in frustration.

The EDEE format was nowhere near standard to anything and confused a lot of people, this format is more legible.  The EDCE files do not have an xml extension, because they are not standard xml. Non standard xml is used for efficiency and portability reasons. However, some one that understands XML should be able to convert the text file to standard xml for the purposes of putting it into the "standard readers",  and then convert it back when they are done. However, I have not tried this and I do not know if the "standard readers" would output the file in the format the game program is expecting as CDATA is a key piece of every text element.  One can also take a free editor like Notepad++ and do simple string replaces to build the appropriate syntax. 

--Mark

(2 edits)

Changing the directory doesn't work. 

.

(2 edits) (-1)

Whatever...if you cannot find it unto yourself to be civil, then you will simply be ignored and you should find a different game to play. We don't have time to waste with insults.

But if you are interested in changing the directory, follow these directions from the manual.

In the additions directory off of the Game Reference Directory, there is a file entitled
AltPath.txt. If you edit this file, changing the first line of the file to the full path for the desired
directory, then copy the file to the Game Reference Directory, the program will create the
appropriate data structure for the game in that directory.
THIS WILL ONLY WORK if AltPath.txt is placed in the Game Reference Directory

You have done something wrong. If you want it to work, please try again.

(2 edits) (-1)

I have never heard of a Game Reference Directory before. What exactly is the Game Reference Directory ??

Here is my current game path ... D:\Games\EDCE\win64\EmpireCombined_Data\Profile - can my profile data go in that empty directory you provided or should my profile be off the Game Reference Directory whatever the heck that is.

So in my terminology, there is the game ROOT directory (Win64) with the EDCE executable and then the game subdirectories.

When I open the game, it says that Version 3 is out. How do I download (where?) and/or upgrade my game software?

I really, really, don't want to subscribe and endure all the advertising that subscribing to STEAM will obviously generate. More spam! I hate advertising. If I register on STEAM, I will bet I will be inundated with all kinds of propaganda about buying or paying to play games and gaming equipment and such. 

Ok, you had to have at least one set of images for a new unit to test the feature. Put it in a zip file and send it to me! Better, update your release to include it in the directory that it goes in ... call it sample for some such.