I know how to fix it. Stop people from being too lazy to mask the whole border of the level. =P

And, I was just joking. I don't need some CTF-bug to be fixed. =3

The flagbug is my only priority with CTF right now. Other bugs like dying on the other team's base will not be fixed as I do not have a breakpoint for it.

It's named floodbug, not flagbug.

This is flagbug.

Flagbug.Flag death.

Wrong. :D

You indeed are.

no u

*calls Derby*

Is it possible to make JCS not let you run or save a CTF level unless there is a border? If it is possible than it should have a warning message pop up. It would also need to have a message that pops up that asks you what type of level you are making. I think it is possible to edit JCS because a language translation of JCS has been made before. It was called JCS PL.

As far as JCS's coding is concerned, no.

(one more reason to start this big project...)

the bug can be fixed by adding masks around levels that cause the flagbug.

Laser fix for TSF now up in the downloads section at J2O:
this space for rent

Hey, how do you install the exe files?

Just so everyone knows, I am personally looking into the flag bug fixing. I think I've got it figured out, although it may be a pain in the posterior to implement it into the game.

Hey I downloaded 1.25i, how do I apply the patch? where is the BackItUp batch file? and is it worth installing if I won't be able to play 1.23 servers anymore- how many people have applied the patch?

Is there a way to make it so hurt events hurt other players in multiplayer?

The CTF flood/flag/whatever bug has been FIXED.

All we need to do now is wait for someone to implement this instruction that fixes it:
Let it also be known that this code has not been tested thus far, because I cannot implement it without Jazz Jackrabbit 2 giving me access violations.

*bumpy wumpy*
Well?

Hey, the smilies have changed...:cool: :rolleyes: :p ;-) ;) :D :o :( :confused: :eek: :mad: :derby: :crimi: }) ...
Ehee hee.

Download UIPS, get the latest IPS file, and use the command prompt to patch it. The usage is:

uips a patch.ips yourjazz2file.exe

I got the UIPS program and I still don't get it...can you give me a hand please, or step by step instructions for idiots.

1) put uips and the 1.25i patch in the JJ2 directory.
2) create a file called something.bat that contains the following:

copy Jazz2.exe Jazz2.exe.bak
uips a jj2125i.ips Jazz2.exe

3) save the file and run it in the command prompt.

And I still think this patch should be called 1.23b.

It's not 1.23 beta, is it?

\o/

Then let's start up a vote and see if I should rename it.

I don't mind, as long as it isn't 1.23. I get confused every time I start Jazz, thinking wether I installed it or not.

It's quite unfortunate that JJ2 has to be a sux about registry keys, because if I was to change 1.23 to 1.25, the entire thing would require a new registry key. I'll change that in 1.25z (if I even get that far).

Good call, UF. I vote yay for renaming. I think it would be a good thing for the patch.

I think it's very vital to rename it. Despite making it less official sounding, it would make it feel more like a real patch, and not a gimmick. Because the '1.25' name mostly shows the contrast about what it is not, to me, and for me, it loses its seriousness.

Also, 1.25 was already started on by the jj2 developers. Not code-wise, I think, but planning-wise it was. This was visible in how they collected ideas for the patch during the J2C/JC time. Naming it 1.25 is essentially having it use an already-existing patch name. It's just not serious and 100% clean, which it should be, for the good of this patch.

I kind of have an 'emotional' stake in this (you might have noticed), as I started up the 1.25 council and brought the source code debate to the community. The forum still exists (want access? you meet the criteria, but you've never asked. it contains *some* useful info on stuff), and it's rather weird to have the '1.25 council' name be suddenly be meaning something totally different. It's essentially copying the name of an idea that has existed since way before these patches. And 1.25 sounds like it's official, while only the code rights owners should have the power to act like they're increasing version numbers.

1.23.1 it is.

The next version of the patch will be called 1.23.1a.

\o/

And that patch will be released only to a select group of individuals. Have a nice day!

If it's only released to a select group of people why bother?
That just ruins the aspect of multiplayer, and will make people hate you(If they dont hate you already for driving Lark away).

You're next, n00b. >)

And that was in fact a joke - it should be released in the near future, only not as a beta.

You can't drive me away.
Unlike Lark, I don't have drums or a life.

Then I will need to make do with the next best choice.

Even though it seems unnecessary now, I agree with Frank.

1.2.3.1a. Fun. :)

Anyone finding anything on adding brackets to red teamchat?

1.23.1 is technically just as "official" as 1.25

Can't you just edit the game name to Jaz Jakrabit?