If I'm writing a script and I want to enable/disable/activate {whatever} a specific item, what is the correct syntax for that? I've tried using %referencename%.enable (ex. - CastleDoorway01REF.enable) but it always tells me the reference can't be found, even if the "persistent reference" option is checked on that instance of the item. I went through several tutorials on the CS wiki, but most of them don't give examples of this. From the few that did, I thought that was the correct way to do it, but obviously I'm doing something wrong.

*bump*

I skipped this last time for two reasons: 1) Usually someone more knowledgeable than me will answer and 2) That seems to be the right way to do it.

Anyway, if you drop an item, NPC, activator, whatever into the render window it will create a reference to it. If you then double click that reference (or right click it in the listing in the cell window and choose "edit") you should get a window of options for that reference. Choosing "persistent reference" in the checkboxes, and then giving it a Reference Editor ID in the top text box, i.e. "CastleDoorway01REF" should enable you to use "CastleDoorway01REF.enable" in a script without an error.

Just remember that it's the "reference editor ID" from this options window, and not the name of the base object that matters.

If that's what you've done, then there's something odd going on. You'll have to confirm the existence and spelling of the reference editor ID.

Thanks Showler - I'll double check everything. It's a huge comfort just knowing that (at least mentally) I'm doing it right.

Well, if I'm doing something wrong I can't figure it out. http://mods.omegacron.com/oblivion/scripterror1.jpg showing my reference, my script, and the error that's popping up. I've been staring at it so long it may be obvious to someone else and I'm just not seeing it.

You can't start reference variable names with a number. switch it to a letter and you'll be dandy.

Oh yeah. That error. I think Oblivion decides that anything starting with a number is a formid, rather than an editorid.

meh, the editor's an idiot It will aways find new ways to baffle me with its eccentricities, but I've learned a fair few of them by now...

Yep, that was it. Does that only apply to references used in scripts? I used the same naming convention for 100+ references so far, but if it's an issue I might as well bite the bullet and change them all.

Either way - thanks a ton for pointing that out. I can't imagine I would've thought of that unless someone brought it up.

best to rename them i think. You might not have to but it's probably a good thing to do.

That's a good example of why it's usually best to post a specific example of what's causing the problem, rather than a general one. The vagaries of Oblivion are baffling to the minds of mortals.

You may want to use "a1" in the future, works great

So it's okay to use numbers in the ref names though? As an example, the mod I'm working on I named a reference SWAS1, then the next one SWAS2.

It''s just the first character that matters.

I read once someplace by someone (maybe fluff) that the first 2-3 characters matter btw - I reserve first 4 to be letters to be on the safe side

Never had any problems with a1. I usually start with a1, then a mod tag (For my comeback of the Dawn mod it's COTD, for powerattack voicemod PAVM etc.) Ex: a1COTDMythicDawnDivider01