I've made this thread because it's clear that the BC community needs more scripters. There are people posting new ideas in here occassionally, but there's nobody around with both the knowledge and the time to make other peoples' ideas work. The logical solution is to do everything possible to help people learn Python, and some of the specifics of BC's Python interface.
PYTHONThe place to start if you're serious about learning Python is:
www.python.orgThis is the official Python home page. You can download the latest version of Python here, if you wish (and if you intend to learn to use the language, I'd heartily recommend it!). Bridge Commander uses Python 1.5.2, so it might be best if you went with this version.
Also at this domain name are links to several good tutorials for learning Python. A direct link to the page with the tutorials on is:
http://www.python.org/doc/Newbies.htmlAnd I particularly recommend
A Non-Programmer's Tutorial for Python for those of you new to the concepts of programming.
Bridge CommanderAs for Bridge Commander-specific stuff.. Well, I'm afraid there isn't really much around yet that I'm aware of. Bear in mind, everyone in the community that knows *anything* started off knowing nothing at all, and it is only trial and error, and sifting through the SDK that we've learnt how to do things!
When making new scripts for BC, this is the process I'd follow to configure my computer:
1. Install a second copy of BC, and patch it.
2. Extract the scripts from the BC SDK (
Available here, I think you need only get V1.1)
3. Start scripting! Just go nuts and try *anything* at all! You can edit the .py files in any text editor, or if you've downloaded Python, you can use the editor it comes with, which has nice features like syntax highlighting and things.
And if it all goes wrong, your main BC install is still safe, and all you'll probably have to do is re-extract all the .py files from the SDK back into the Scripts directory! Nice and easy!
As I said, please feel free to use this thread to ask more questions, but please, try and keep the scope of your questions small! Asking for help with one particular problem you've found while working on something is far more likely to get a positive response than popping in and asking "How do I program it so that the saucer can seperate?". Where possible, if you have code that's playing up, attach a file so that people can have a look at it and try to work out what's wrong (You may need to change your file's extension to .txt, or zip your file, to attach it to the forum)
This thread should not be for other scripters to do all your work for you. It should be for other scripters to help you become a better scripter, so that the number of people working to make the game better can start to increase.
Originally Posted at BCU by Sim Rex