some basic scripting questions

[King Class Scout]

1. where are the stock weapon scripts, like basic projectiles and disruptor shots (otherwise, you'd have to ask permission for EVERYTHING)
2. do you have to ask permission from the mesh maker, as ususal, for redoing an un-hardpointed ship?
3. does a scratch hardpoint have to be saved in PYC in order for the MPE to read it? (it keeps ignoring my scratch hardpoints)

[X_TheUnknown_X]

Firstly, BC Scripting might be the best place to ask for scripting help. But to answer your questions:

1) The stock weapon scripts are just the ones named PhotonTorpedo, QuantumTorpedo, etc. Besides, you shouldn't have to ask permission to use someone else's torpedo script as a start as long as you don't copy any of their torpedo effects/settings (because all torpedo scripts hace the same parameters). Also, the BC SDK has a 'scripts' folder which has ALL the stock files in there. (it's under 'SDK/Build/Scripts/Tactical/Projectiles')

2) On BCFiles, if the mesh is under "Public Domain Meshes", then permission isn't required (as far as I know). For other meshes, a permissions section should be added in the readme or description. Otherwise seek the creators permission.

3) The Model Property Editor will open and save in .py and .pyc files. It's best to save in plain .py, because .pyc are magically created by Bridge Commander when you start the game. I don't know why MPE should ignore your hardpoints, unless there is nothing in them in the first place.

[KrrKs]

My MPE loads ".py" well. Try to load Hardpoints Manually and don't forget that the actual Subsystems are located in the "scene Root" Mesh property on the right.

[King Class Scout]

I leave my practice HP's with the model files on my desktop for easy access (as I did with the Gabriel).  the one I worked on was completely ignored, even though the file is there (it's not complete, of course, I needed a break).  MPE did the same thing to the Gabriel the minute I added a Plasma shot emergency weapon to the Gabe.  it completely ignored, and left totally blank, the hardpoint side, even with sceneroot on.

unknown: SDK?  lemmie guess, it's on the disk...i haven't gone through the disk's files, yet.

Edit: oh.  DUH!  sorry,  my head is empty sometimes

[MLeo]

Considering 2 out of 3 questions are about hardpoints, Modding is the correct forum.
Only the first question is a Scripting question.


1. All stock py files are to be found in the SDK.
2. If the model comes as is, so without a hardpoint, then permission requirements can usually be found in the readme.
3. No, you only save in py format. Only BC will create a pyc, which you do not have to include if you want to redistribute your mod.
While MPE can load pyc files (if you specificly ask it to load one), it is important that you save your hardpoint in py and not pyc format, otherwise BC might crash, or worse, delete/overwrite your work.

[King Class Scout]

*chuckles as translates your sub-title* appropriate.  at least YOUR coding skills aren't super antique, like mine (Basic, color basic [Tandy], some apple 2 coding)

I'm not gonna try and release it (it's the unused Klingon D9), but keep it for myself.  i colored it up, some, as plain greys are kinda bland.
I found my goof.  i had two copies of the ship property, deleted one, and it nailed both.

btw, your Diamond BC projectiles saved my butt with that one, I typoed in the HP.  too bad your shipdef tutorial thread is too old to reply to, I'm having a hard time understanding it.

thanks everybody, it's hard to know where to put issues like this.

[MLeo]

What is the link to the ShipDef tutorial?

At any rate, you can use BCUT to create a new ship plugin.

[King Class Scout]

my bad.

this old tutorial.  http://bc-central.net/forums/index.php/topic,3216.0.html
I've read it over several times, and I still get confused.

[MLeo]

my bad.

this old tutorial.  http://bc-central.net/forums/index.php/topic,3216.0.html
I've read it over several times, and I still get confused.

Please elaborate on what confuses you (better direct it through a PM/email). And I'll see what I can improve.