AI-ing (.py files, coding, nose-orienting R+D, and help)

[Avalanche]

Put range around 500 to ENSURE that it starts right away.

[Naryar]

99 should work.

Maybe it's how you wired it ?

[TheUnknownRobotics]

99 should work.

Maybe it's how you wired it ?

No, I wired it "Spin" (No quotations), and I put  99. I'll check it again.
Also, some of my robots spin very late anyways, even with 99 range. What should I do?
(By late, I mean as soon as the robots are touching, the motor spins, doing, like, little to no damage.)

[Naryar]

99 should work.

Maybe it's how you wired it ?

No, I wired it "Spin" (No quotations), and I put  99. I'll check it again.
Also, some of my robots spin very late anyways, even with 99 range. What should I do?
(By late, I mean as soon as the robots are touching, the motor spins, doing, like, little to no damage.)

Are you using an analog or switch instead of a button ?

[TheUnknownRobotics]

99 should work.

Maybe it's how you wired it ?

No, I wired it "Spin" (No quotations), and I put  99. I'll check it again.
Also, some of my robots spin very late anyways, even with 99 range. What should I do?
(By late, I mean as soon as the robots are touching, the motor spins, doing, like, little to no damage.)

Are you using an analog or switch instead of a button ?

I used a button, and I did, in fact, name it Spin. So I have no idea what's wrong.

[Badnik96]

Do your robots have "weapon" values in their binding lines? If they don't, their weapons won't spin.

[TheUnknownRobotics]

Do your robots have "weapon" values in their binding lines? If they don't, their weapons won't spin.

... Damn it. I'll be right back. Thx Badnik.

[cephalopod]

If you don't wanna find the actual component numbers to use in the weapons section, just put 0 - this corresponds to chassis so the bot will always try to spin the weapons as long as the range is triggered (even if the weapons aren't there)

[TheUnknownRobotics]

If you don't wanna find the actual component numbers to use in the weapons section, just put 0 - this corresponds to chassis so the bot will always try to spin the weapons as long as the range is triggered (even if the weapons aren't there)

Thankfully, it works now. (For some reason, I'm feeling more doubt of starting a tourney, now.)
Hopefully I'll remember this in the future.

[Jaydee99]

I may have asked this before but is there an AI for a thwacker hammer thing and a spinner?

[cephalopod]

FBSInvertDir will do what I think you're trying to do.

[Jaydee99]

Thanks

[RedAce]

Can someone help me out here? Whenever I start the game with this AI for this bot, the game crashes. What am I doing wrong?

https://gametechmods.com/Robot_Exchange/BW/jaydee99_Kitten.bot

Code: [Select]

    list.append(("Kitten","Omni",{'nose':math.pi,'invertible':True,'range':50,'radius':1,'topspeed':100,'throttle':100,'turn':100,'turnspeed':2.5,'weapons':(0)}))

[yugitom]

I don't know but this line works:

Code: [Select]

    list.append(("Kitten","Omni",{'nose':math.pi,'invertible':True,'range':99,'radius':1,'topspeed':100,'throttle':100,'turn':100,'turnspeed':1,'weapons':(0,)}))

[G.K.]

Did you remember teams.txt?

[yugitom]

Did you remember teams.txt?

Doesn't matter. I tried it with teams.txt and it still didn't work. The new AI line works, for some reason, though.

Edit: Just saw what Chris said. Yeah, the comma after the very last 0 needs to be there.

[G.K.]

Yeah, that comma is prolly it.

[RedAce]

Not sure why that works, but that doesn't matter. What matters is that it works. Thanks guys!

[Naryar]

there is a comma missing after the 0 of weapons and i am quite sure this is it

edit: 2slow

[yugitom]

edit: 2slow

Not even. You just didn't read the fact a solution was found.