First Timer Advice

[Tollana]

Okay....

I've finished my 3d model and got it in the correct format and i realise .....

I have NO idea how to do Python and don't know how to create any of the scripts.

Can anyone direct me to any tutorials on creating these specific ship scripts? (If they exist)

Thanks!

[King Class Scout]

download the BC SDK from filefront.  there's no writing necessary, as the Model Property editor included lets you fill in the blanks.  the SDK also contains all the default scrips, including projectiles.

others can give you better advice.

[tiqhud]

Many people are going to say to edit your Hardpoint in Notepad, resist the urge, while Notepad is a good way to view the Hardpoint, MPE or Bcut are best at editting , because with Notepad it is just to easy to make an error and the ship wont load or you crash to desktop.

{Bcut for some minor adjustments}  but MPE for major work.

[webxro]

notepad is for people that are sure that they can't make a mistake , so i will never use notepad 

[King Class Scout]

only a pro in th Python language should type it out the long way.  this is what the MPE is for; non-programmers.

[Mario]

only a pro in th Python language should type it out the long way.  this is what the MPE is for; non-programmers.

Where did you come up with that conclusion?!?

Why would anyone type something by hand if there is an existing working tool to be utilized? Using tools means less chance of making mistakes and discovering mistakes the hard way while testing is a pain, there are no debug modes to be used for BC scripting. There's no need to reinvent the wheel.

@Tollana
Check this page: http://bridgecommander.wikidot.com/creating-and-adding-ships-general-overview
Tools you need are: BCUT, TDIE and MPE. With these 3 tools you don't need to do any scripting -- unless you're planning on adding some new techs.

[King Class Scout]

Where did you come up with that conclusion?!?

Why would anyone type something by hand if there is an existing working tool to be utilized? Using tools means less chance of making mistakes and discovering mistakes the hard way while testing is a pain, there are no debug modes to be used for BC scripting. There's no need to reinvent the wheel.

I'm an old skool nerd/geek, sov.  I come from the 5 and a half floppy era, where you had to type everything out for the simplest program, AND had to know every nuance so you didn't almost literally blow everything up

anyway, have fun, o noob to HPing.

[Mario]

I'm familiar with how it was maybe like in the past. I had as a kid Commodore 64, Amiga 500. But technologies advance so rapidly and if you don't keep up you'll end up being a "dinosaur". In my business time is money and I have to keep up with the latest technologies. Besides you can't live in the past.

[JimmyB76]

10 IF X = 42 GOTO 40
20 X = X + 1
30 GOTO 10
40 PRINT "X is finally 42!"

for the lulz

[King Class Scout]

*chuckle* your probably not old enough to feel old when the tech does this   besides, I already AM a dinosaur...my tech expertize stopped in the 90's

good luck, Tollana.

[Mario]

your probably not old enough to feel old when the tech does this

Absolutely no. If I did that, I'd be out of the job in the next few months (overstatement but you get the idea). Microsoft advances its tools and publishes new IDE's every 2 years and I'm a professional Software ASP.NET Developer.