• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

Zsar1

Major
52 Badges
Dec 19, 2014
659
199
  • Arsenal of Democracy
  • Victoria 2: Heart of Darkness
  • Victoria 2: A House Divided
  • Darkest Hour
  • Crusader Kings II: Jade Dragon
  • Hearts of Iron IV: Cadet
  • Hearts of Iron IV: Colonel
  • Crusader Kings II: Reapers Due
  • Stellaris: Digital Anniversary Edition
  • Stellaris: Leviathans Story Pack
  • Hearts of Iron IV: Together for Victory
  • Crusader Kings II: Monks and Mystics
  • Hearts of Iron IV: Death or Dishonor
  • Age of Wonders III
  • Stellaris: Galaxy Edition
  • Hearts of Iron IV: Expansion Pass
  • Stellaris: Humanoids Species Pack
  • Stellaris: Apocalypse
  • Stellaris: Distant Stars
  • Shadowrun Returns
  • Crusader Kings II: Holy Fury
  • Battle for Bosporus
  • Stellaris: Ancient Relics
  • Stellaris: Lithoids
  • Hearts of Iron IV: La Resistance
  • Stellaris: Federations
  • Stellaris
  • Europa Universalis IV
  • Victoria 2
  • Europa Universalis III: Collection
  • Crusader Kings II: Horse Lords
  • Crusader Kings II: Conclave
  • Crusader Kings II: Way of Life
  • Stellaris Sign-up
  • Crusader Kings II
  • Crusader Kings II: Charlemagne
  • Crusader Kings II: Legacy of Rome
  • Crusader Kings II: The Old Gods
  • Crusader Kings II: Rajas of India
  • Crusader Kings II: The Republic
  • Stellaris: Megacorp
  • Crusader Kings II: Sons of Abraham
  • Crusader Kings II: Sunset Invasion
  • Crusader Kings II: Sword of Islam
  • Europa Universalis III
  • Divine Wind
  • Heir to the Throne
  • Stellaris: Synthetic Dawn
  • King Arthur II
  • Stellaris - Path to Destruction bundle
I have taken the liberty of creating an organisation and repository for CORE on GitHub.

Motivation is to decouple the release process from specific individual people, who may disappear without notice.

Also, the ability to formally declare pull requests will ensure that individual people's finished work will - once declared as ready - always be visible to whoever intends to create a release, even if said people are not present at the time.

Conversely, after declaring a piece of work ready, the contributor does not need to care about preserving the state of affected files: Accidentally submitting files with further, incomplete changes cannot happen, so work may continue at any time without heed for the integration process.

CORE contributors may PM me their GitHub name for access to the organisation.
Read-only access to the repositories is free for everyone.
 
I am currently contemplating how to setup the repository structure for the mod files themselves.

Idea is to keep directories separate, if seldomly changed together. To that end, my first impression would be something along the lines of
  • Softcode
    • .
    • ai
    • db
    • scenarios
  • Map
    • map
  • GFX
    • gfx
  • Config
    • config
With the first indentation corresponding to repositories and the second one to sub-directories of mod-CORE2.

Note that I threw the base directory in with the softcode rather arbitrarily, as it does not seem worthwhile to create an extra repository for that. None of these files seem to be relevant for the mod to function, though, so mayhap they should rather go to the Installer repository.

This does not yet consider the existence of several different Graphics Packs for CORE, but as far as my impression goes, all but the B&W Graphics have been discontinued anyway, so it might no longer be sensible to actually differentiate here.

Furthermore, before we do much work with this setup, we might want to consider incorporating CORE for different games, e.g. CORE 0.4 for HoI2:A.
If we want to accomodate for this possibility, it would be easiest now, before the repositories are created. If we do not, however, there is no need to burden ourselves with additional infrastructure we would not use.
 
Last edited:
The color graphics pack is still an option, though I'd have to review the model changes from 0.6 onwards (brigades mostly). But I still have the masters, and kept them (largely) up-to-date.
 
Someone has been busy I see. Is there a CORE version for Gary Grigsby's War in the East, or should the repository mayhap rather be outside the organisation?
 
*raises hand*

I was wondering whether you were the same as the Denniss on the Matrix Games forums... :p
 
Yeah - I got that one. ;)

Well if you need any help on WitE2 I'm game, I guess...
 
I am still around. Just been taking a break from a continuing failure to improve JAP vs. CHI.
I have stuff I have worked on, but I would need to merge it all into whoever has the master files, I guess.
 
I have the masters nowadays... So if you have any material that needs inclusion just send it over to me. I've created a preliminary build for 0.70.8 last Monday, but it's not distributed widely yet, so we can easily add to it.
 
@Hagar : How much do these master filesets differ in layout from a normal installation of the mod?

I would deem it most comfortable for git users to create the repositories as mirrors of the intended layout, but if these masters (say, for the purpose of installer building, mayhap) are significantly different, then mayhap rather mirroring their layout would be more appropriate.
 
Which one do you mean? CORE's, or WitE's? The latter is pretty straightforward, all images go in the '\Dat\Art' directory, and that's it.
 
Well, considering that I am not yet involved in anything regarding WitE... including such basics like owning the game, hrhr...
I ask about the masters for all CORE products we want to offer installers for, that is to my knowledge, the main mod and any graphics pack.
 
Last edited:
I want to add all files as a mirror to the original setup. But so far I haven't been able to find out how to do it...
 
Mmh, if I remember right:
  1. Create repository on GitHub
  2. in local folder:
    Code:
    git init
  3. in local folder:
    Code:
    git remote add <name> <repository url>
    [*]in local folder:[code]git push
with <name> some string without whitespaces, e.g. CORE_AoD and <repository url> the url of the created repository, e.g. https://github.com/mod-CORE2/Installer.

Tutorial

- I think there is a browser GUI way to do it on the GitHub site, but would have to try that out myself.
 
Does the current AOD Release version still requires placeholder text files for AI/switch AI files in the main AoD game folder? Same question for ship icons/silhuettes.
The AI files are no problem but the ship silhuettes did influence main AoD as these were the actual Core versions and not adapted vanilla versions so silhuettes and ship types in vanilla did not match anymore.