Today we have a huge update with lots of fixes (31) and it's all thanks to your bug reports and help. And of course new content is also there.
CaesarIA is remake of Caesar III in the big world of Ancient Rome. You can build the small village with some of gardens and a workshop where you want. You also can perform tasks from emperor or build the large city and broke attacks of barbarians, Egyptians or carfagens which want to steal your goods and kill your citizens! You also can pass the company from original game. The good lock with high walls will help to cope with any invasions.
The fighting system of game continues and develops the principles from Caesar III. Legions of soldiers can be sent to any point of the card, but don't submit to direct instructions of the player, and work independently. Depending on a situation soldiers can recede or be reformed for the best interaction.
The agriculture, extraction and production of goods will demand adjustment of production chains and if the necessary goods can't be got in the city, your trade partner can always sell it to you using land or maritime trade routes.
+ loading maps from original Caesar III.
+ save\load game state
+ create\destroy buildings and construction
+ constructions influence on desirability around
+ migration(in/out) of citizens
+ warehouses and granaries for storage of goods and products
+ damages\fires of buildings
+ entertainment constructions (theaters, collisions and B'day)
+ imperial trade network with the computer-cities
+ fishing, agriculture, extraction
+ Information layers for city states
+ prefects, engineers, trainee, soldiers and other
+ employments simulation
+ houses grow depending conditions around
+ health care and water supply
+ military buildings and war action
Linux, Windows, Haiku (future MacOSX,AndroidTab?)
+ Now it is possible to download the game alpha version.
CaesarIA realizes all main mechanics, but still some important features aren't made yet completely, for example:
- the relations with emperor and gifts,
- wrath and blessings of gods,
- realistic financial system (salaries, purchase of goods, job search)
- specification of citizens, preservation of parameters of thoughts and formation of requirements
- seamlessness of the world
- computer players (cities) and simulation of a distribution network
- network (web/local)
With your support i'll create remake of great game and to add new opportunities.
CaesarIA: devide et empera
Original article here (https://bitbucket.org/dalerank/caesaria/wiki/Reverse engineering Caesar 3 (part 2))
Created by dalerank
Translated by Anastasia Smolskaya
I hope that the previous post Back-Engineering Caesar III, with the description of the algorithm of creating textures from the resources of the original game was welcomed by the inhabitants of habrahabr.ru. This article describes the format of maps, algorithm of selection and order of tiles for drawing, creation of the final texture.
If you are familiar with tiles you can skip the following part of the article.
Tile is a picture of a fixed size created so that while you draw near other tiles you don’t create any “stiches”. Here is an example of grass from the game Caesar III©
If you put them together in a definite order and add a little bit of texture with trees then you’ll get some part of surface. And if you add to this picturesque image another kind of tile, say, the one that depicts a road, you can put together a basic map.
You have probably noticed that the presented tiles have a shape of a diamond not a square. The purpose of this is to create the image with dimension (depth). That kind of tile looks as if it was turned to the viewer and as if it spreads to the depth, bidirectional image gets third dimension. To create the effect of dimension the width should be two times less than the length of the image. Tile base in the game Caesar III is 58x30 pixels, this is the minimal size of the tile which is operated by the game engine. On the first phases of remake creation we got one unpleasant effect, textures in the game are created without taking into account transparency and when displayed on the screen without additional processing we got the following result.
The way out is as follows: you can use a mask, for example the color of the farthest left symbol is taken as transparent or textures should be complemented with an alpha channel. In the original game we used the first option, in the remake – the second: textures are prepared at the stage of resources upload.
MapMap is an array that defines the position of the tiles on the layer and their parameters. In the simplest case the map is a matrix MxN with each element having an identifier (number, figure) from the so called “tiles palette”. Tiles do not necessarily have successive position number, numbers of tiles are divided between several intervals and named areas. Thus, for example, tiles of earth, trees, water, cracks and grass have the indexes from land1a_00001 to land1a_00303. In the game Caesar III it is allowed to use square maps from 30?30 to 160?160 tiles. Tiles are positioned the map so that its upper boundary is the “north”.
In order to draw the tiles on the screen it is important to take in account the distance to it, if you just draw tiles in the order they are placed on the map you’ll get a misconvention because some part of tiles was not drawn in time.
The order for drawing tiles is shown by the following image.
This image is generated from the following tiles drawn in the correct order.
Drawing a town
Additional conditions that occur while drawing a town.
These conditions complicate the process of drawing and create additional rules for drawing.
How to draw
Map format of Caesar III
The objects that are shown in the town in file *.map include first five data blocks. Read from the beginning of the file, read the data one by one without gaps.
short tile_id — contains identification elements, each identificator corresponds to its texture. For example, identificators group 246-548 corresponds to textures land1a_00001-land1a_00303, these are textures of earth, trees, etc., which were described before.
byte edge_data — the array contains information about the size of the object which has texture in the array tile_id
short terrain_info — the array contains characteristics of surfaces for each tile, earth, water, road, wall, etc. (complete info here)
byte minimap_info — basic info for creating a mini map, it also takes part in some calculation during the game as a so called array of “random numbers”.
byte height_info — this array describes the height of the tile over the surface, 0 – for land, 1 – 15 pixels, 2 – 30 pixels and so on.
More details about the game Caesar III© and the development of the remake can be found on our wiki at bitbucket.org.
Special thanks to Bianca van Schaik for help in writing the article and providing materials.
And in the end a small test screenshot that depicts Etrurian spearmen vandalize the City of Fountains: