Warzone 2100 Forums

Iluvalar wrote:I was going to suggest the same syntax as the one in that file, except you dont need replacedComponents at all. Just use resultComponents with that optional bit ":Laser2PULSE-VTOL"

but in my case you able set multiplie replacements
when you get assault gun it can replace HMG, TMG, MG

latest version of research.ini for multiplayer research.ini - price of research capped by 450 (as in original) - components still can be replaced and all exiting replacement was kept latest version of my patch: https://github.com/crabster/warzone2100/commit/0eedb78e38b7c3a9840430f24ff44bf3f30338f6 c...

Does it matter which component replaces which other component? Just have a list of components that are caused to be obsoleted by that particular research... eg obsoletedComponents = comp1, comp2, comp3 i tried it :ninja: when pulse laser become researched, we need replace flashlight with pule laser...

What was wrong with "replacedComponents"? each result component could contain link to "replaced component" in what format this link should be present in .ini??? here is windows-converter for research.ini: ResConverter.zip [/size] (executable inside, dont open, dont run, and even...

Need advice about how to store replaced components in research.ini
I do not want to use 1 more file.

I'm not quite understanding the localization stuff, even though it was probably already discussed; all these "name = " and "name_en = " confuse me a bit. Can we use _() in ini files? name_en was added only as information and actually not used in loading codes i need per's advice...

@Shadow Wolf TJC well you understood correct :) my opinion: better re-implement this feature through functions/scripts current (old) implementation in resultcomponents.txt has some issues: e.g. you cannot replace more than 1 redundant components per 1 result components. hm.. i can keep this function...

research.ini present already research.in [/size] but it needs some advices and corrections Looks nice! Where there are no values, you should just drop the keys as well. Also it would be nice to have the full name (from strings.txt) in there. see research.ini [/size] my patch ready, but it was write...

i see problem in supporting low resolutions (640*480?)
well i'm not fan of mobile devices


@Mr_T pretty nice UI

@Iluvalar agreed with your ideas

research dramatically fast in early game and stupidly slow in later game

Per wrote:...in the future-to-be research.ini file, so time will be untouched

research.ini present already [/size]
but it needs some advices and corrections

Am i right to believe that while price is capped at 450, research points required are still uncapped? That is, if we decrease research points to 450 together with the price, it will take much less time to research them, for the same price as before? Price and time will be made separate. e.g. user w...

My opinion: "Another idea is to halve the excess over 400" - for Multiplayer Many things in later game totally unbalanced. For now is ok to set price just a bit higher, but in futher patches price of each research in later game can be reviewed. e.g. price of Satellite Uplink can be increas...

Well, hardpoints can shoot above other hardpoints too, so that's not to make towers better… :? hardpoints cannot shoot through other hardpoints this feature was silenly implemented in 3.1 if you want make stronger defenses you need 1) 1 line of bunkers 2) 1 line of towers 3) 1 line of hardpoints th...

Hardpoints can shoot through towers but towers cannot shoot through hardpoints

Originway wrote:nothing works for windows on windows

i'm using visual studio to build warzone
but you need install some stuff (like Qt)
well windows os is not liked by wz community