Thread revived for a new issue! Please see post #10.

Is there something setting warp back to 1 again? Maybe post your whole script so we can look at it.

Here it is. It's just strange that after figuring all this out (with the ever-helpful MW Scripting for Dummies) it's this one thing that stops the show. But I guess that's what everyone starting out says. I changed some variable names, too. Thanks again.

Begin zs_winescript3short OnPCEquipshort alreadyshort waitfloat wtimerfloat ftimershort dofadeshort warpreadyif ( MenuMode == 1 )	Returnendifset already to ( GetPCCell Cellname ) ;check if you're already thereif ( OnPCEquip == 1) ;you've equipped the bottle	if ( already == 1 )		MessageBox "The cork is stuck."		set OnPCEquip to 0	else		MessageBox "You drink from the bottle of wine."		set wait to 1		set OnPCEquip to 0	endifendifif ( wait == 1 ) ;initiate warp timer	if ( wtimer < 3 )		set wtimer to ( wtimer + GetSecondsPassed )		MessageBox "wtimer is %f" wtimer ;tells how much	endifendifif ( wtimer > 3.0 ) ;fade out	set wait to 0	FadeOut 3.0	set wtimer to 0	set dofade to 1endifif ( dofade == 1 ) ;initiate fade timer	if ( ftimer < 3 )		set ftimer to ( ftimer + GetSecondsPassed )		MessageBox "ftimer is %f" ftimer ;tells how much	endifendifif ( ftimer > 3 ) ; fade in	set dofade to 0	set ftimer to 0	set warpready to 1	FadeIn 3.0endifif ( warpready == 1 ) ;warp	set warpready to 0	player->PositionCell 0 0 10 0 Cellname	MessageBox "warp complete"endifEnd zs_winescript3

[EDIT] I managed to fix the issue. I took your advice about something setting warp back and I added another if check before ( ftimer>3 ). Seems to be working 100% now. Thank you.

Just a quick glance tells me that if the timer ever happens to stop exactly on 3, your script won't work.

That hadn't crossed my mind. Until, of course, it happened. Precisely 3.0000000. :rolleyes: But I'll have to remember that.

If your script is attached to a bottle, then StopScript won't stop it. It only works on scripts that were previously StartScripted elsewhere.

Correct. StopScript only works for global scripts not local ones, because the object the script is attached to is continually calling the script. If you want to stop a local script from executing after the action is done, it's best to check for the completed condition at the top of the script and create a return. That way, once everything is done, the script will just hit the return and never continue again.

I use this often with NPCs with long scripts. If they're dead, I make a check for that and kill the script with a return at the top.

So you are saying that I cannot "fully stop" a script on an object unless the object is removed. But I can halt the script at the first line. Okay. This is making more and more sense. My bottle script is perfect now!

What if, say, I attach a script to a bottle that, when used, StartScripts another script then removes the bottle? Would that make the started script a global one? I don't intend to do use this the moment, but it seemed a good question to ask.

Yes. I've done a similar thing to simulate the drinking of a scripted potion. Because you need to skip equip to make sure the entire script on the potion is executed, you then need to start a global script to finish off the job once the potion is swallowed. The script started from the potion's local script is a global one which can be stopped using the StopScript command. You then use the global script to remove the potion from the player's inventory, play the swallow sound (because it won't be played otherwise because you skipped equipping the potion) and finish off whatever you need to do.

In fact, in the case of scripted potions, the best thing to do is have the local script only use the StartScript if you only want it to perform after the potion is swallowed, and relegate the rest of the action to the global script that it starts.

Hey again, minor bit of thread necromancy, but I figured it was better than starting a new one. I've got a new problem, and the documentation I have isn't being very helpful.

I'm using MWSE to insert names as strings into message boxes, and the buttons are options you can toggle on or off. The issue I need to fix is that you can't tell whether an option is on or off. I want to add a suffix to each button that says (On) or (Off). But nothing I can find in the material I have says how to append strings onto strings.

Basically, does anyone know how to take a string like Option Name and add an (On) so it will read Option Name (On)?

Can't you just use xStringBuild (ie setx stringvar to xStringBuild "%s (off)" stringvar)?

That was the first plan, but it's messy and slow. The menu has eight options, and I have to check all of them in big ol' if-blocks. But so far, that looks like my only option. Thanks anyway.

Ah, I see... Sorry, I can't think of anything better