Instructions for releases 1.3 to 1.5
The level files are in the
bubbob/levels subdirectory. They come in two flavours:
.py. The former are MacBinary files from the original MacOS9 game. The latter are the levels that we did ourselves. To make new levels, copy for example
CompactLevels.py to a new name, and open it with any text editor. The structure should be fairly simple to understand even without knowledge about Python. Just don't try to look at
The server can be run in the command-line only; try
cd bubbob and
python bb.py --help.
Pygame. This is a cool gaming library for Python. It is available for quite a lot of platforms. (Also see the kitchensink link above for MacOS X.) This gives the nicer results, so if you can install it, go ahead! You'll get transparency effects on the bubbles!
MS Windows. (It means that Bub & Bros runs natively on Windows; but you can also install Pygame on top of Windows for the nicer bubbles
The X Window system (the graphical environment of Unix/Linux). The native X Window system is pretty fast under Bub & Bros, so try this if you have a slow Unix/Linux machine. Note that you could also try it on MacOSX's X11 (I guess you need to start
display/Client.py from an
xterm command-line for this to work).
GTK (the Gnome environment) if the PyGTK bindings are installed. Unlike the other drivers this one offers you the ability to scale the window, zooming its content in or out. Use it if your screen has a specially large or small resolution.
A Java-enabled web browser. No installation required. (But you won't have the nice background musics when playing in the browser, so I'd recommend that you try one of the solutions above as well, to really enjoy the game.)
The client can also be run from the command-line; try
cd display and
python Client.py --help.
BubBob.py. If you can't make sense of it feel free to send it to us (address below).
10.0.0.42. The various programs (client, server, meta-server) are doing their very best to connect to each other nonetheless. If you cannot connect to a server, see next section.
First note that if a local connexion doesn't work, you should try using the meta-server:
If it doesn't help, and if you're technically inclined, read on.
Local connexions: if you cannot see a server in the list of local servers, then:
machinename.domain.com:1234, as displayed on the server when it starts).
During a normal connexion (not going through the meta-server) the client needs to open a TCP connexion to the server. The server can be configured to listen to a specific port ("TCP server port" of the configuration page) if you can let this port in through a firewall or router.
Servers listen to HTTP as well. This is used for both the local BubBob pages (if you have a very restrictive firewall on your own machine then you might not be able to connect to your own machine, unless you let that port through) and for remote clients to which the server sends a Java applet. You can force a port in "HTTP server port". It default to 8000 if this port is free.
The server sends UDP datagrams to the clients during the game; if these ones don't pass through, they are re-routed over TCP, so it should just work. Nevertheless you might prefer UDP for responsiveness. The client can choose on which UDP port it will listen for incoming datagrams ("client incoming UDP port" of the configuration page) if you can let this port in through the firewall.
If a client has no way to establish a direct connexion but has an
ssh account on a machine near the server, he can do:
ssh somewhere.domain.org -L1234:servername:4321
servername:4321 is the full name of the server, and
1234 is some randomly choosen local port. Then you can connect BubBob to
127.0.0.1:1234 using the
Go button on the main page. In this setting, if you can still let UDP datagrams enter, then configure "client incoming UDP port" to be not only the port but the whole name of the machine (or router) that the server must send the datagrams to.
Connexions using the meta-server (with the "Internet server page" from BubBob's main page) work generally better, as long as the server and the client can independently connect to the meta-server (which is at
codespeak.net using TCP ports 8050 and 8055). Firewalls and routers generally allow this. The meta-server will then co-operate with the server and the client to synchronize their connexion. (The meta-server will not route game data between the server and the client, though.)
With the help of the meta-server, we have more techniques to try (in order):
users.sourceforge.net, or join our IRC channel
Please don't hesitate to contact me. As Bub & Bros interacts with an external web browser to run, there are probably configurations that will break it. It has been tested on Windows ME, MacOS X and Linux PCs, but this is no guarantee that it will always work -- far from it.
The Bub's Brothers Home page