Profile of ferwiner

As the supression of maxim has been absolutely butchered in the notes, I would be for a muni costing supression increase ability. It should be effectively better than current maxim during that ability but can deal less damage.

Another idea would be a toggle between supression and damage mode - like shermans AP/HE rounds. That way you could use maxim as a defencive supression platform with little damage or change it into "assault mg" and boost its damage loosing most (all?) supression.

I would also support the ideas connected to maxims water cooled nature like ability that allows it to shoot constantly, not in burst for some time, or a centaur-like sweep. These abilities also should have some kind of drawback - for example the sweep could supress everything in the angle of fire but without damage and pin.

It's not completely fixed, but this is the best we could do at this point.

Hey, at least it doesn't trigger counter-barrage, any more.

Actually, is there some kind of list of units that trigger it? If so I would be interested to see it.

A doctrinal unit to counter a basic unit.

Not really. If the brit doesn't use any emplacement boosting commander ability then the emplacements can be quite easily countered by mortars or ISG. Not to mention the flame ht. What I said above applies to team games of course for the reasons explained in my last post.

@ferwiner

I am not an expert modder and even less of a scripter/coder (so excuse my ignorance), but I can try to describe what a conflicting ID looks like and what I've been doing to solve it. Within the many .xml files in the mod directory there is a line:

<uniqueid name="pbgid" value="1073741918" />

Every new "thing" (whether it be a unit, weapon, ability, anything) is created then it is given a new unique id. If something is copied with the intention of replacing an original vanilla coh2 "thing", this is copied.

However, my guess of what happened in the last patch is a bunch of new "things" were created where the vanilla files added new ids that modders have already been using.

It seems that the IDs are up a the 1,000,000,000 (billions) and just adding another digit (ten billions) isn't enough of a fix. What I've been doing is changing the billions digit with a 2, so it is at 2 billion (I'm counting on the game not reaching two billion "things"). This kind of works as long as IDs are 10 digits, but it isn't always the case for every "thing". It ranges from 1 to 1billionsomething which some people might have.

Is this something maybe you'd be interested in creating a solution for? If not, maybe as a solution for Relic, is there a way to make it so newly modded creations get a different notation for IDs than the base game? That way in the future such a problem doesn't happen again.

The reason why adding another digit won't work is quite simple - these numbers are most likely being read as signed 32-bit integers and these range up to 2,147,483,648. Or unsigned but then the limit is only twice that.

As far as I understand the problem the solution that would work in the way mod builder expects it would be to find the highest number of all uniqueid elements in the file and the highest number of the ones supplied by SneakEye, then take the bigger one.

Next, it would be enough to find all uniqueid elements that have numbers equal to the ones on SneakEye list and replace them with succeding numbers starting from the one calculated before + 1.

If so, then this is a very simple programming task and I'm sure can do it in some of my free time. The thing is though that I need to test it before giving it to you guys. For that I need a conflicting script from some really big mod, or even more than one mod, to make sure I know the structure of these files well and so there won't be any corner cases I won't spot. The one supplied by Olhausen is not good for that purpose becouse it uses only a single uniqueid tag.

Btw If you want it done, please use the reply button when replying to me, otherwise I don't get the notification and may forget about the thread.

EDIT: looks like relic just released a hotfix for your problems. So I'm probably not needed here any more

RitaRush,

is your comment now a new joke or something really confirmed?

It's not a joke but it has nothing to do with relic - just a commender designed by community that is never going to be implemented.