News NPC AI update

not skynet but scary enough. (it bet anyone worried about climate change has never really heard about 'agile development'!)

great news, way to go!

On a serious note if anything this is a good reminder of what kind havoc could be created by AI in real systems, whether purposely or via bugs.
 
Are powerplay NPCs going to be looked at?

NPCs from allied powers were attacking players last I looked, preventing many players from exercising their power bonuses (Aka Bounty Hunting) because they would end up being attacked by an allied NPC and losing merits in self-defence.

Very much this. Hope this is on the todo list, not to far down.
 
Don't want to put a damper on this wonderful praise heading in Zac's (Lord praise him) direction.

But what the heck happened to the beta and bug testing. Was it just skipped on this one??

All hail to FD.
 
So if ships were firing Rails like Pulse lasers, why weren't they just combusting into a ball of flames? Did the Rails also have the heat build up of a Pulse laser?
 
I just had a terrible feeling..., seems like we, the community failed our job finding those AI bugs during 2.1 Beta. Am I right? Have we failed our purpose?

Luckily the brillant sir Mark Allen smacked those bugs for us!!

I'm so sorry for that dear Frontier. I promisse I'll do better myself during next Beta!:)
 
Last edited:
Not just weapons, I've been repeatedly outmaneuvered by NPC ships that normally can't turn well.



All the ships can be manoeuvred much better than we can, simply due to our very human reflexes and processing/reaction/input times.

However, if you feel you have encountered a manoeuvre bug by all mean bug it on the support forums so it can be looked at.
 
I just had a terrible feeling..., seems like we, the community did a bad job finding those AI bugs during 2.1 Beta. Am I right? Have we failed our purpose?

I'm so sorry for that dear Frontier. I promisse I'll do better myself during next Beta!:)
It seems that bug could be that complex that it didn't expose itself till release. Certainly players couldn't pinpoint this clear enough to make good reports and for FD to understand before mass deployment.
 
I just had a terrible feeling..., seems like we, the community did a bad job finding those AI bugs during 2.1 Beta. Am I right? Have we failed our purpose?

I'm so sorry for that dear Frontier. I promisse I'll do better myself during next Beta!:)

Nope. This was not happening in any of the beta releases. This was introduced between the last beta version, and final release.
 
Don't want to put a damper on this wonderful praise heading in Zac's (Lord praise him) direction.

But what the heck happened to the beta and bug testing. Was it just skipped on this one??

All hail to FD.

Betas only happen for major updates, 1.x and 2.x, not for patches :)
 
This actually sounds way more complex than anyone predicted :eek: Impressive debugging devs! It opened a rare window into crazy possibilities of potential NPC uprising! :D
Debugging is code is rarely simple, as errors are always subtle, and may manifest effects that show up far removed from the original error.

Fixing code, in my experience, means spending hours tracing execution paths and sanity checking everything as you go, until you find the "+" where you should have typed "++"....



grnbrg.
 
I just had a terrible feeling..., seems like we, the community did a bad job finding those AI bugs during 2.1 Beta. Am I right? Have we failed our purpose?

Luckily the brillant sir Mark Allen smacked those bugs for us!!

I'm so sorry for that dear Frontier. I promisse I'll do better myself during next Beta!:)

If it was networking bug it was probably caused when they moved update to live servers or live servers have heavier load that cause the issue.
 
I'm sorry if I didn't catch it in Zac's update but are the uber npc's been removed from the game now or are we still able to encounter them until the bugfix is released?
I'm on Xbox btw but serverside changes are effective for both platforms no?
 
Really pleased to read Zac's update but the bug has cost me in the region of 13m in Insurance claims since 2.1 :-(
 
Back
Top Bottom