1. Home
  2. Development
Log in to post
Load new posts
  • TheDogT

    Warning for those upgrading to v2.6+

    1
    1 Votes
    1 Posts
    543 Views
    No one has replied
  • LaFayetteL

    RFC: merging skins with maps

    17
    2 Votes
    17 Posts
    2k Views
    C
    @LaFayette The alternative skin for 270BC is an example of changing also the units. There may be others. Here you can find a map-skin for RSoC that is actually about making the map bigger: https://github.com/Cernelius/red_sun_over_china-big_skin The current map-skin feature allows changing everything in the skin, and that is good. What is not very good is that it obliges you changing everything, so forcing duplication if you don't actually want to change everything. It is true that most map-skins are only about changing the map details, but I think this is beside the point (Of course, some things are more used or useful than others.).
  • C

    TripleA Rules Sets

    15
    1 Votes
    15 Posts
    3k Views
    LaFayetteL
    @LaFayette said in TripleA Rules Sets: What would be ideal is to have a table describing different behaviors by rule set. We are actually on our way there. We have example maps that follow each rule set, all we need to do is to start teasing apart the behaviors that are different and then answer for each map, "does this follow that behavior, yes or no?" If we find that some rule sets are only very slightly different, simpler is better. The 'v3' moniker will be difficult to drop, if we can keep it simple and say "old edition", "revised edition" and "new edition", it could be easier to adopt. At this point though, without knowing what the rule sets actually are, it seems to be a first priority to know which rules are in each rule set before we do much of anything else.
  • LaFayetteL

    Storing Maps as Folders only rather than as either Zip or Folder

    10
    4 Votes
    10 Posts
    2k Views
    djabwanaD
    @Cernel As we unzip a file, we will be doing a lot of checks (are all the required folders there? is there a centers.txt, etc.?) and as part of that process, we could enforce a casing convention. I have a tool that fixes capitalization. When I got image assets from @GenerationKILL sometimes the casing was a bit off, so I would just run this tool and it would conform every unit to a convention like this: Unit-Name.png regardless of the OS and regardless of the original naming. We could implement a similar normalization process at the map parsing level (though it might be hard to get map makers on the same page about which casing convention should be used). https://github.com/jdimeo/triplea-map-tools/blob/master/src/main/java/jdimeo/triplea/util/FixFileNames.java
  • T

    GameData.acquireReadLock usage?

    3
    0 Votes
    3 Posts
    862 Views
    T
    So, would you be ok with removing some locks if it can be shown that the data is actually read only? I'm currently looking at ResourceList which is what GameData#getResourceList returns. The class has only one setter and it is only called during the game parse process and a test method. The data that ResourceList stores is a map of Strings and Resources. And Resource is a value object. ResourceList doesn't appear to need any sort of read lock since I don't see any way for it to change. If I see locks around GameData#getResourceList, can I just remove them? Would you like me to tag Resource and ResourceList somehow (such as @Value) to indicate that they are read-only objects?
  • LaFayetteL

    Replace Console Logging with a File

    25
    2 Votes
    25 Posts
    4k Views
    TheDogT
    @LaFayette Dont forget to add triplea.log to the list of files to uninstall.
  • aardvarkpepperA

    Questions from a know-nothing beginning programmer/developer

    8
    0 Votes
    8 Posts
    2k Views
    LaFayetteL
    That said, is there a particular reason (other than a chunk of code not really necessary to functionality) that save game files don't work that way? Java serialization was once popular, it was an initial design decision to use it, it was somewhat easy. We would actually like for save games to work more like you have described. It's a very large project, that is all, and we have a large backlog of small and large projects that we are working on and collectively there is not that much development labor available. Re: performance requirements These are the wrong things to focus on. First focus on functionality, what are you going to built? What value will it provide, how will it be used? You need a good product for anything else to matter. Then I'd encourage to stop worrying about specs. Simple and well done architectures are fast and perform well. Simple code is usually fast code. Once you have a reasonable design in place and functioning, then you can start analyzing where the performance bottlenecks are and where to go to optimize. It's a ways to get to that point, and once you are there the process is to measure, change, repeat. Humans have generally very bad intuitions for where performance problems will arise. It's also easy to try and fix all performance problems as optimization problems when they are really design problems. One can look at a block of code and wonder "how can I make this faster", and sometimes the right answer is, "how can I avoid needing to execute this in the first place?" That is why keeping things simple and working is very important, it lets you reason about what your code is doing. For example TripleA does a lot of calculations twice, why? Because there are 15 layers of call indirection separating the two which creates several thousands of lines of code in between the duplication. Bottom line OUr time is short in just about every way imaginable. I'm pretty sure and somewhat regrettfully going to say, if you want something that interoperates with TripleA, it's potentially one of and likely all of: untractable and/or a truly huge project We have wanted to for example to allow TripleA to run on web browsers, or phones. That project is probably 3-8 years away from being completed if it were started today.
  • T

    Combine casualty selection dialogs?

    2
    2
    1 Votes
    2 Posts
    899 Views
    TheDogT
    Its a good idea, I like it.
  • T

    AA Auto Casualty documentation?

    1
    1 Votes
    1 Posts
    752 Views
    No one has replied
  • T

    AA and targets with multiple hit points, how many dice?

    8
    0 Votes
    8 Posts
    2k Views
    LaFayetteL
    I think you may have to look at which maps have the combination of properties set to see how it is used. I can imagine a few different variations of how such behavior would be used. Generally, if the intent were to be able to shoot down a multi-hit-point air unit, it would make more sense to me for the AA to do more than 1 damage.
  • T

    When should support be allocated?

    10
    0 Votes
    10 Posts
    1k Views
    LaFayetteL
    Sounds right, though I think this is a simpler way to think about it: before a unit rolls, it looks to see if there is an available support, if so, it consumes that support.
  • T

    Why does all aa attack values must divide into attackAAmaxDieSides?

    5
    0 Votes
    5 Posts
    882 Views
    T
    @alkexr , thanks for those forum posts. It does look like this warning is no longer valid.
  • N

    I would like to start helping out with tripleadevelopment but don't know where to start

    6
    2 Votes
    6 Posts
    2k Views
    N
    @LaFayette said in I would like to start helping out with tripleadevelopment but don't know where to start: Are you familiar with doing feature branches in git? Were you able to compile and run the game from scratch? No to both of those. I guess I need help.
  • MirkoBrunerM

    Implementing UI Visual

    Moved
    32
    1 Votes
    32 Posts
    10k Views
    MirkoBrunerM
    @RoiEX I have read your specs, Issue seems to be closed at least for now. How do we proceed from that? Any Idea? I have already my questions about your navigations and other annotations. Regards @RoiEX .
  • F

    PR help

    14
    1 Votes
    14 Posts
    2k Views
    LaFayetteL
    There are three ways to merge branches: merge fast forward merge rebase git merge <remote> <branch> and git pull <remote>/<branch> AFAIK are the same thing and are both merges. git pull --rebase <remote> <branch> is a proper rebase. This is the one you should prefer to avoid having 'merge commits'. A fast forward merge is really similar to a rebase, and you do that with a -ff flag to merge, ie: git merge -ff <remote> <branch> There is also a proper 'rebase' that can be done. AFAIK these two are the same: git pull --rebase <remote> <branch> and git rebase <remote> <branch> Unfortunately it is fundamentally a bit confusing as it depends on exactly how the rebase is done and with which flags. This is a place where a GUI can get in the way.
  • F

    Development setup

    27
    0 Votes
    27 Posts
    7k Views
    F
    @Trevan I am glad you know your way around! I never would have found that.
  • aardvarkpepperA

    Is there a flowchart or similar for the AIs?

    7
    0 Votes
    7 Posts
    1k Views
    aardvarkpepperA
    @TheDog Thanks. Quite handy.
  • TheDogT

    Factory/Town building in version TripleA v2.3+

    7
    1 Votes
    7 Posts
    1k Views
    TheDogT
    Awh shucks (looks down & shuffles feet)
  • ubernautU

    First stab at 2.0 AI

    2
    2 Votes
    2 Posts
    728 Views
    ubernautU
    @redrum so here's stab #3 AI got moscow again in stab #2. this is v3 btw figuring that the most advanced version of the game that AI can play effectively. playing as allies with no bid maybe i should started as axis but i wanted to see the AI's initiative and figured giving some kind of handicap to AI was probably warranted. noticed that the AI is definitely stronger than before but still seems to have some weakness in the area of protecting transports. i know we've discussed it before but seems like there must be some way to prevent AI from spending all it can on facility repairs as well makes the AI very susceptible to strat bombing. autosaveBeforeEndTurn.tsvg
  • T

    Usage of "Submarines Defending May Submerge Or Retreat"?

    7
    1 Votes
    7 Posts
    1k Views
    C
    @Trevan Yeah, this is a very old problem. V1.III is not something I can be sure, but I'm almost sure you should be able to submerge regardless whether or not you are able to retreat. As far as "Submersible Subs" goes, my suggestion was to keep the name as an archeproperty and split it into a series of new properties.

Recent Posts

  • RogerCooperR
    RogerCooper

    @LaFayette What happens if there is bad update, that breaks part of the game. How can we go back to good prerelease version?

    read more
  • ubernautU
    ubernaut

    @LaFayette ok so maybe all that wud be needed at this point then since the menu is icons i’d reverse the up arrow that wud make it more obvious that thats where you go to download

    read more
  • LaFayetteL
    LaFayette

    @ubernaut we kinda hijacked this thread, but be what it may - finally found where those links are defined. They are only at the bottom of the "recent topics", AFAIK only displayed exactly on the homepage. I removed them all, it's not a place to really expect to see a lot of links and they require maintenance and are a bit dubious...

    read more
  • LaFayetteL
    LaFayette

    And I guess the maintainer/maintainers will retain the capability of skipping a scheduled recommended release if they feel like it's better not to (in case the current release having some serious regressions).

    If the upcoming recommended release has a serious regression, then so would the version that the new players are downloading. The way to deal with regressions will be to immediately start rolling back code updates until the regression is removed. It's easy to restore those code updates, but the reaction will be to start rolling back as soon as any issue is discovered and then roll forward with a confirmed fix. Thereby, regressions should be resolved essentially immediately, not with fixes, but with rolling back. That buys time for doing a fix properly, avoids trying to patch broken code with potentially more broken code, and reduces how many other updates that go into the code base that could be broken themselves (it's a lot easier when something breaks if it's obviously the last thing that was merged, it's a lot more difficult when we are testing for the first time months after the fact and there are multiple things interacting with each to cause a breakage)

    How about the recommended release being automatically skipped if there is one or more open GitHub issues with the "Regression" label on it?

    That idea was floated, the regression label might become obsolete. It will depend how significant an issue is, but generally the response will be to remove all recent code updates until the culprit is removed.

    (I obviously also assume the recommended release will not happen if it is the same as the previous one, like in case it is seasonal and no new version of TripleA was release in 3 or more months. Right?)

    This is in part a rationale for 6 month cadence. Helps avoid that situation and reduces the frequency for players being asked to update

    read more