Notpron Forums

Kinda funny how he only addressed the LEAST important point of my post, besides I was only doing that from memory so something probably got confused somewhere... anyway, the petty stuff aside...

My main comments were regarding goal size and the clock bug... will we see a solution to the clock bug that in my opinion is the most troublesome bug still in the game? Goal size, again, is at the mapper's discretion and the NADBL mappers will tweak to the popular liking so for all intents and purposes we can just screw the defaults. Personally, I think our NADBL-24Beta2, or whatever that map is called, has a very sensible goal size for 2.4.

Bottom line, clock bug is of utmost importance to fix along with regular "bug" (can't fire ball when you have it) and the no hammer bug which are probably one in the same anyway.

well, goal size is wonderful the way it is. when the defense allows you an open shot from 40 meters away, you can score. when there is a good keeper in the goal, you can't. it just works great this way and it feels so real (football being real), but hey. in my plans the aiming of hard shots will be a lot harder anyway
i dont support smaller goals at all

i've never encountered this clock bug, and I play a lot....never heard of it either 0_o


Anyway, dunno what will be done. Cata said we'll hack 2.4 up, and get it out, and he said he only has time until the end of this week...on the other hand nothing was done for days and I haven't seen him for 2 days either. Don't ask me, I'm just sitting here and hoping, and even praying sometimes.

The player attitude that gets a long to me is just this "there is a bug, fix it, kthx done"....as if it's not involved with major work or anything, and all know that there is basically no team...

The clock bug is some strange recurring problem that I can't isolate on the BuD servers.

In a nutshell, the game ends with the clock showing anything from 0-40 seconds left on the clock.

Damndest thing.. I can't figure it out. Unless it's the hardware or something, I stripped things down to a bare deathball server and it still messed up at random.

Biggest pain would have to be the 5min+ mapchange when replays are enabled. That one has gotta be a garbage collection issue or something.

i remember that from some servers long ago. but we do not have this on any of the servers we regularly play on....well i didnt have it for a long time

The mapchange prob affects all the NA servers. Wierd as hell.

yeah, getting worse after every match, i know it. some cache problem, it should be cleared after a match :S (i think)

I know all of the current bugs (if you'd call them that) will go away once the full version of 2.4 is released, but for the time being I think it would REALLY help the entire community if a few things were cleared up. It would also help the way 2.4 is looked at because if people see annoying bugs then they might be turned off. But any who:

1) Invisible ball - when someone is close to you and you charge and they catch it, the ball disappears but someone does have it. The only way to tell is the mini map.

2) Shakey - In 2.3 if you started to charge a split second after the defender or whoever hit you, it wasn't an OC. But in 2.4 you have to wait a crapload of time for it to not shake. Shakes also usually just roll in front of you instead of randomly going in any direction.

3) Magnet - If someone is behind you they can catch the ball or .2 it. I find that to be the most horrible thing about 2.4 beta; something has to be done about this because it's heavily affecting gameplay.

We don't need the flashy ball effects and karma ball etc., just gameplay issues fixed. If people see that the beta looks good, then they'll be tempted to try the full version.

o\

27 views and no posts? You know it's called a discussion for a reason. You discuss your thoughts and opinions in here.

all I can say is that I agree with all you said.hopefully they will be fixed.

2.4 is the bug

You listed a few terrible "bugs", so I agree of course.

4) DavidM

unfixable

The map change problem might be to do with the end game replays - I know the DB code does some crazy things to allow the clock to stop during a replay as well. It may be caused by the time which was "skipped" being added on at the end, perhaps, or just some dodgy code whcih allows the server to merrily tick along for a long time before the map actually decides that the wait's been long enough and it should change.

As for the code - I'm sorry I've not been around, but I have actually been quite busy the last few days - like I said, I'm taking a break. I'll put the code I've written up for David, but I just don't have the time to properly make 2.4, and I put too much pressure on myself to make the things I produce *perfect* - hence I'm taking a break from everything for a while. I didn't mean to leave everything hanging but it's just happened that way. The code itself is rather messy and unfinished as well - it might not be worth it, most of the stuff I've done relates to the dodgy ball trail code anyway. Still, e-mail me, I'll send you the stuff I have. Sorry for disappearing, but I really don't have much free time =(.

Now now now let's not flame anyone in particular, it's not DavidM's fault that these bugs are here. It would be his fault if he refused to do anything about it

2.4 isn't so bad, I personally don't like it but with these few changes I honestly think it'd be so much better.

I think people don't like 2.4 now because of these bugs. I'm very sure that you'll hear positive comments if these fixes are done.

I agree with insane completely. Its hard for us to get an idea of how the version is really shaping up with the major bugs listed above. If we had these bugs fixed we could more easily give our opinions on the direction the game is going in.

No coders eh? Bummer...