Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[allison]

Just accidentally slew the Data Miner. I feel guilty

Would it be possible to warn before swording a neutral robot? Something like the current ramming confirmation would be nice.

[Kyzrati]

Hehe, some people do that on purpose all the time, though!

Consider it done for the next version. I've heard this potential feature occasionally mentioned from time to time, not necessarily for this scenario, but even for just accidentally attacking random bots blocking hallways who then alert something nearby. (We seem to get some new confirmation every release or two )

I'll make it optional in case some players don't want/need it.

[zxc]

I gotta say that swording neutral bots is something I do all the time, and I wouldn't want a confirmation on that. To prevent what you said, I suggest leaving melee weapons off (weapons can be toggled with the ' key) while you're exploring, and only turning them on when you're intending on swinging that thing.

[Kyzrati]

Right, that's what I always suggested players do in the past, and why confirmation there hasn't become a feature earlier, though perhaps it makes sense to have it on as the default? It'd be an option, as I mentioned, though the toggle would be in the cfg. Or perhaps the default should be off? Argh, defaults are hard sometimes xD

[DDarkray]

It's swording major NPC, allies, and unpowered robots that are a big problem for me. I would like a confirmation for them, but all other robots I wouldn't really mind.

[zxc]

It's swording major NPC, allies, and unpowered robots that are a big problem for me. I would like a confirmation for them, but all other robots I wouldn't really mind.

Ah, this I can understand. It would be nice to have.

[Kyzrati]

Okay, added an optional melee confirmation/delay for attacking neutral or inactive robots! (...coming to a Beta 1.3 near you )

[DDarkray]

Yes! You're da bomb!
Now I also need to somehow convince my allies to not kill those unpowered robots...

[Kyzrati]

Ah, a not-so-veiled attempt at trying to stack on an additional request, I see?

Not completely sure what you're referring to in this case, though, since allies don't attack unpowered bots. I think maybe you're talking about temporarily disabled bots? In the case of disabled bots, in some cases you would want your allies to attack them, such as mid-battle where they'll eventually reawaken to attack again--may as well take them out first.

Or maybe you're referring to dormant bots? (There are a number of different statuses, each with their own term as shown on the robot info page.)

[DDarkray]

Ah, my plan has been foiled!

Sometimes, I see some random robots being pushed by serfs, and I want to be able to rewire them. However, when I have my allies with me, they still attack even though the disabled robots pose no threat. (I felt so sad to lose a potential programmer ally) 

[Kyzrati]

Okay there you go, those in particular are definitely a good candidate... I'll see what I can do.

[Kyzrati]

Hm, actually, are we sure they still do this? I made a change a while back to their behavior in terms of attacking disabled bots in general, and on testing multiple different scenarios now I don't see them doing it. So either there are some even more specific circumstances required, or this is no longer an issue at all.

[DDarkray]

The specific robot that attacks disabled robots (being pushed by serfs) is the enh. grunt ally that is provided when coming out of DM branch. See if this is still a problem.

[Kyzrati]

It would take a while to set up that particular situation since I don't have a way to manually create one of those conditions, and from what I see in the code that shouldn't really be the case--the AI doesn't initiate attacks on any new hostiles that are disabled.

There are other more complicated situations though, so if anyone sees something related to this (AIs attacking a bot of a status they probably shouldn't attack) drop a screenshot and description here and I'll explore it further.

Most of them have been corrected by now, though I do believe there might be at least one case left (not yet sure if it's something that would be adjusted or not, but we'll see).