Lol, Jacob isn't good at coming up with file names.

[noob007]

In the buildism folder, there are files named a.class, b.class, c.class and sometimes go all the way to z.class... Even folders are named a, b, c, etc.

Either come up with a better naming system, or don't separate your code into so many files. :p

That's a suggestion.

[Kieron]

I know, right.

[Micky]

Why would he want to do that? I mean, they are just files, we dont care about files ,we care about the game :p

[noob007]

But he will lose track of them if he continues this way.

[Micky]

Meh, he seems smart enough for me!

[Jacob__mybb_import1]

I didn't name them that way, the code optimizer/obfuscator does that.

[noob007]

Oh.


Why did you use an obfuscator?

[toast]

Oh.


Why did you use an obfuscator?

To stop people from modifying stuff after decompiling...

[Login]

In the buildism folder, there are files named a.class, b.class, c.class and sometimes go all the way to z.class... Even folders are named a, b, c, etc.

Either come up with a better naming system, or don't separate your code into so many files. :p

That's a suggestion.

In my opinion, it doesn't matter how you name your files. a1.class b1.class and then b2.class it's quite simple and much faster to code.

[noob007]

In the buildism folder, there are files named a.class, b.class, c.class and sometimes go all the way to z.class... Even folders are named a, b, c, etc.

Either come up with a better naming system, or don't separate your code into so many files. :p

That's a suggestion.

In my opinion, it doesn't matter how you name your files. a1.class b1.class and then b2.class it's quite simple and much faster to code.

Not when you don't know what's in each file.