Toolset Static Plugin

[oldgrayrogue]

Well, I specifically would like to know if we can use this:

http://nwvault.ign.com/View.php?view=NW ... tail&id=92

It claims you can create quests with NO TOOLSET OF SCRIPTING KNOWLEDGE.

If this can be adapted to our ACR (it says it can be made to use custom scripts) then, presumably, anyone can create scripted quests with nothing more than the ability to type and an imagination.

Please advise, thanks.

[Castano]

AK send me a static then, thanks.

OGR I would love to, can we discuss in #alfa-tech?

[oldgrayrogue]

AK send me a static then, thanks.

OGR I would love to, can we discuss in #alfa-tech?

Sure I'll hop on when I get home from work tonight.

[Castano]

ok in the meantime I discussed with tech and the plugin in will not work as it does not assign the right conditions to the conversation.

[Zelknolf]

Oh dang, and I was just about to post my explanation in the other thread and it got moved.

Yeah, it does persistency wrong (or, rather, wrong for us; it works if it's a single-server project without an established persistency scheme). Using it won't work with other ACR stuff, and it'll run everything unbatched and uncached through NWNx4 (which was the source of ALFA's pre-2010 crippling lag).




That said, you need no scripting knowledge to make a quest with the ACR. I'd like to make the "no toolset knowledge" claim of the plugin-- but, well, the plugin was lying. You need to learn how to use the toolset in order to use the toolset plugin, or anything in the toolset. But you don't need to be a technical person to work in NWN2, and you can make simple statics even if you're starting with no knowledge (you'll acquire some on the way, for sure, but you don't need to start with any); it's all things that you type into, they're named what they are, and you drag bits around a very-visual scene to say where they go.

We folk in tech have already written all of the scripts, and have done everything that the plugin has done except the extraneous bits of interface-- when you hear about one of us writing code for a static quest, it's either because we're being overly fancy (like I wrote code for the Beryl quests and the Ruqel orc scouting/assaults on BG, but you can tell from just looking at those that someone was feeling fancy when writing them) or because we're writing the scripts for non-technical people to plug into their non-technical toolsetting. Promise you'd find help if you asked.

[FoamBats4All]

What Zelk said, with this emphasized:

Promise you'd find help if you asked.

We've done live stream tutorials. We have 0 new creatures because of it.

We've done custom tools. We have like 1-2 new spells because of it.

We've done documentation. It rarely gets read.

ALFA has the tools, documentation, and folks willing to help guide builders to what they want to create. We're there on Skype, live streams, #alfa-tech, or whatever else is needed.

At this point creating yet another tool that will never get used seems like a waste of time. The toolset is easy, and if people spent a fraction of the time trying to learn it that they spent throwing their arms in the air, saying how shitty it is, we'd have already built all of Faerun.

[Castano]

I'm not in favor of creating another tool.

I do still need NPCs, the conversation files and items created for any static that you want to make. It's easy enough to email them to me.

[oldgrayrogue]

OK I will try. But please all of you amazing tech people understand:

I have read a lot of the documentation you guys have created including the tutorials

I have tried to use the toolset and even learned how to make custom armors pretty well

I have tried to make statics and even spent a couple of hours with Wynna and Curm on IRC guiding me through the process

I am a fairly well educated person

I still feel lost when I open and try to work with the toolset.

So I'll try, but Cast it may take some time.

[Castano]

thank you for trying.