45 replies to this topic

[ThetaOrion]

I have a fairly good feeling the bugs with the teleporting are relic issues as I have experienced them in human vs human games without the AI mod.

--

Well, I have only experienced the disappearing Monolith or Monolith teleporting bugs with an AI present, but in my case, it was the human player who was experiencing the bug.

Anyway, you are right, it's probably a Relic hardcoded bug that Arkhan and Larkin can't touch, but every once in awhile, these guys surprise me and find a workable solution while they are in there tweaking the AI. Sometimes they fix something in the AI and it seems to magically carry over into other things as well -- some kind of global variable thing that they clean up or stabilize, most likely. It's happened before with other things, from what I remember, but obviously not if the whole thing is hardcoded and locked in stone by Relic.

Wouldn't surprise me if Thud were to write, "we can't do that, because it's a Relic bug," and it wouldn't surprise me if one day Arkhan writes, "I found what was wrong with the nearly damaged teleporting Restored Monoliths, and I fixed it, for the AI at least." I have seen it go both ways.

Edited by ThetaOrion, 17 November 2006 - 02:00 AM.

[Malkor]

sup battle scarabs

Yup, they tried to get into the SM base. The necrons also had a monolith that needed repairs but they just ignored it.

Yeah, they're completely ignoring the damaged monolith that came back when it was damaged in restored mode.

edit -

To clearify, the mono was "killed" by the SM. It was stunlocked by terminators and forced to do its 20% emergency teleport thing, putting a tier3 monolith with 20% of its life back in the necron's base. After that happened, all of their workers suicided the SM base. They rebuilt the workers, but don't seem to notice that monolith. Additionally, they aren't upgrading the other two they have to a restored monolith. They do repair other stuff. They also do have a 20/20 16/20 army in their base waiting for action.

Attached Files

•  relic00041.jpg   1.15MB   24 downloads

Edited by Malkor, 17 November 2006 - 03:39 AM.

[thudo]

Hmmm.. the Scarab Builders should have repaired that Monolith as it approached its base. Odd..

[Malkor]

The monolith DIED as in it was returned to tier3 status by getting too damaged, so it didn't approach its base, it was teleported back via the emergency mechanic (NOT the AI's mechanic, what happens when you "kill" a restored monolith).

[thudo]

Oh.. thats completely different.

[ArkhanTheBlack]

The monolith is a bit buggy. I'm aware of three problems with it which seem to be hardcoded bugs:

First is the monolith not getting repaired by the builders for some time although they've nothing else to do. This can take minutes, and eventually they 'get' it suddently and repair it.

Second is the monolith not getting upgraded to restored status for some unknown reason. The buildcontroller tryies to build him, but the buildplan fails since there's no valid build channel found. What often helps is when the other two monoliths are upgraded. One of those always seems to work.

Third is the monolith not getting upgraded to tier3 because he 'thinks' that tier 2 addon was not researched. But tier2 was already researched and the monolith on the field a 100% tier 2 upgraded monolith.


And speaking of necrons:
The lord has a tendency to get stuck even on open field when ressurected. Although I've also seen ork gretchin squads getting stuck, so that's not a specific necron problem.