Bitfighter 019b bugs

I found a bug. When I try to place the text Bitfighter, I'm forced to stare at several spaces before the word. It works in-game though

Also, when I updated my level Six Stars in Pleiades the screenshot doesn't update, though I assume this may be on purpose.

In Two team capture the flag, left a soccer ball item at 0 0, it caused the flags to also spawn at the soccer ball item.

When listening to your own music, /mprev fails to play those tracks. /mnext works

[watusimoto]

Could you please explain the first again?

See http://bitfighter.org/pleiades/levels/view/225 for the first one

[Skybax]

Umm.... just move it?

kinda funny i reported te msuic bug a few builds ago but it slipped through.

1 more music bug. if game music is playing and a server kicks you to the menu, the music for the menu does not play.

Pasted LineItems rotate around the old centroid until the editor is refreshed (you go out of the editor).

new bug

Robots...
canSeePoint and forcefields do not work right? My drones (Bot) do not see the point if an active forcefield is in the way.

[Skybax]

I thought that was fixed last release?

well they gotta fix it again!

some stuff on this page, not so much bugs but anyway
http://bitfighter.org/luadocs/class_rob ... c019783675
bot:setenergy(num) does not work.
bot:sethealth(num) does not work.
setloadout tells you to do Weap1, Weap2, Mod1, Mod2, Mod3
bot:setThrust(speed, pt) appears to have antiquated information by mentioning angles when the only variables are speed and the pt in question. I know there used to be a third type of serThrust but for now we only have setThrust and setThrusttoPt(pt)

well they gotta fix it again!

some stuff on this page, not so much bugs but anyway
http://bitfighter.org/luadocs/class_rob ... c019783675
bot:setenergy(num) does not work.
bot:sethealth(num) does not work.
setloadout tells you to do Weap1, Weap2, Mod1, Mod2, Mod3
bot:setThrust(speed, pt) appears to have antiquated information by mentioning angles when the only variables are speed and the pt in question. I know there used to be a third type of serThrust but for now we only have setThrust and setThrusttoPt(pt)

What? These work fine for me. Are you sure you are typing bot:setEnergy(num) and not bot:setenergy(num)? Lua is cap-sensitive.

[raptor]

Case-sensitivity matters!

The setLoadout() documentation has been fixed.

thanks, set energy and health work now

so.

the setthrust thing is still up

http://bitfighter.org/luadocs/class_rob ... e25e4d3060

See? Comapre to wiki

void setThrust(vel, angle)

- Set robot's velocity to vel (0-1), at angle

void setThrustPt(vel, Point)

- Set robot's velocity to vel (0-1), toward Point.

void setThrustToPt(Point)

- Thrust toward Point, but adjust speed in an attempt to land right on point, and not overshoot. If Point is distant, setThrustToPt() will cause robot to go at full speed.

Right now here is some code from ME. Target ship loc is a ships position..

  Code:

           bot:setThrust(speed, targetShiploc)
 

The wiki is actually really outdated

[raptor]

OK. In preparation for 019c, please post any other little things you find. Here is the status of the bugs in this thread:

Fixed or ignored (for now):
- (Intended Behavior) Soccer ball adds spawn point
- (Fixed) /mprev command doesn't work
- (Fixed) centroid recalculation of LineItems
- (Intended.. Maybe) bot:canSeePoint + FF interaction

That leaves these:
- (Cannot Duplicate) Placing the "Bitfighter" logo renders wrong?
- (Cannot Duplicate) Screenshots fail to update in pleiades
- (Bug) Lua docs cannot handle multiple method signatures, like with bot:setThrust(speed, angle) and bot:setThrust(speed, point)

@tazinator, can you verify that these are still bugs?

- (Intended Behavior) Soccer ball adds spawn point
> In flag games?
- (Intended.. Maybe) bot:canSeePoint + FF interaction
> looks like a bug to me. you can sit on the laser beam and it still won't see past the forcefield until you kill the base

That leaves these:
- (Cannot Duplicate) Placing the "Bitfighter" logo renders wrong?
> I can't duplicate either
- (Cannot Duplicate) Screenshots fail to update in pleiades
> thought that was fixed. idk either

What about
- Losing Game time seconds in editor
keeps happening to me, dont care because it's one second at a time and sounds like you know about it already (timer bug?)

[raptor]

tazinator, can you be more (and very!) specific on how to duplicate your game time bug?

[Skybax]

I had that timer bug at one point, as well. The levels would randomly (after editing) change the times from, say, 10:00 to 9:57. And then if you tried to change it in-game again (since you can only change in increments of 1:00) it would never go back to even.

Skybax > actually, if you hold shift you can do smaller increments of five. works on walls too (inc 1)
to get it even again, i bring time all the way down to infinite and then just put it where it's supposed to be

[raptor]

Please tell me more specifics of the timer bug.

There was a timer bug in 019a that involved saving/loading a level and the game time wasn't saved properly. I fixed that in 019b (or at least I thought).

[sam686]

When changing time limit, did you know you can type in a number for minutes?, press enter, and type in a number for seconds?

The timer bug happens when you test from editor, save, then reload level. If not testing from editor, the bug does not happen. Should be fixed for 019c which may comes out soon.

The editor GameType's timer was somehow counting down when testing level, and only shows up when saving and reloading level.

I think Raptor fell behind a few hours... I fixed timer bug last night.
http://code.google.com/p/bitfighter/sou ... e08077e032

probably intended: dowonload a map using getmap, and then use getmap on that same map again it will overwrite any changes you made

[raptor]

Ha! thanks sam686

tazinator, yes that is intended... I think. But maybe it makes sense to check if the file exists first and rename the downloaded one differently.

nother bug
go to the map Highway by sam686. select everything and use the scale tool to make it bigger. Let's say... by 2.
(control shift x)

nothing happens. it only works going smaller
even if you filter selection by doing only all speedzones, or all spawns, or all polywalls, it still won't work.