129 replies to this topic

[Nertea]

That's very cool. I'll have to test it out at some point. Do you know if anything there is BFME2 specific? IGNORE_PARALYZE_NUGGET for example might be onse such command, as I don't think there's such a nugget in BFME1.

[Radspakr Wolfbane]

I posted up a list of the enums a while back.
I'll have to have a look.

Found the linkness

Edited by Radspakr, 30 December 2009 - 08:13 AM.

[Nertea]

New infuriating problem:

I've run into an issue with buffs (leadership, various effects) being replaced by others. This isn't a simple "two overlapping buffs interact and replace each other" issue.

What happens is as follows: I play a game as normal, and build a number of units, etc. Leadership and the like display as normal. However, eventually I hit a point (seems to be random, but who knows?) where new buffs won't be drawn. New here means ones that I haven't seen before in the game. These buffs all get replaced by one of the "old" buffs (already been drawn). So, i use a power which has a buff involved, and instead of that, something random appears, like a leadership buff. From this point forward, ALL new buffs will look like this one. Old buffs will be ok.

Note that this also affects enemies - I've seen the AI's leadership buffs replaced by whichever is being used too.

I haven't the slightest clue as to what's going on. The most logical thing would seem to be a buff limit, but buffs are just objects with a specific kindof. Nothing special...

-edit: New info:

-The point at which replacement begins is approximately 12 buffs into the game
-The buff that is used to replace subsequent new buffs is the same as the FIRST buff used in the game

Edited by Nertea, 01 February 2010 - 10:28 PM.

[Rob38]

Very strange... do the actual leadership effects work though? Have you tried different graphic settings just to see if the number of buffs changes?

[Nertea]

The various spells' effects seem to work just fine, and graphic detail doesn't change anything.

[Nertea]

New question! I'm coding a structure that is supposed to spawn a unit, then replace it at a regular interval up to a max if it dies. The issue is that the code doesn't seem to work right.

Behavior = SpawnBehavior ModuleTag_SpawnFighters
	SpawnNumber			= 3
	InitialBurst			= 1
	SpawnTemplateName		= MordorTestBeast
	SpawnReplaceDelay		= 80000
End

I would think that this means that we should spawn one unit at first, then every 80000 mscs spawn another one, up to a max of 3. However, this actually results in all 3 spawning at once. Anyone have any experience with this? Or suggestions on how to accomplish the same effect?

[Kwen]

So... kind of like creeps? They are built all at once, then replace over time if they die...

[Nertea]

That's what happens with the code above, and it's what I don't want. They should be spawned one at a time (which is what I'd think that initialburst should mean - set it to 1, and only 1 spawns initially), and then replaced like creeps.

[Kwen]

Sounds to my like the line InitialBurst = 1 is broken.

[Nertea]

New mysterious problem:

I've been fiddling about with treating a horde object as a hero with some success. I worked out all the bugs except one, which I've never seen before. Basically, the horde exits the citadel and then sits there, unselectable. It doesn't proceed to the rally point or anything. However, if you build another hero from the citadel, the horde unfreezes and works as normal. It appears that they're acting like all members of the horde haven't finished exiting yet and are holding before going under player control.

I tried to get around this by making the citadel constantly spawn dummy units every second or so, which I thought might force the horde to think a hero had been built and therefore unfreeze. This didn't have any effect, on further research another hero has to be built (tested by sticking a unit built button on the citadel and building units vs. heroes). Ideas, anyone? I will continue trying to solve it.

Edited by Nertea, 10 August 2010 - 08:07 PM.