Guild of Writers

It will not do anything in Blender if it is written for 3DS Max. It would have to be totally rewritten for Blender until you end up with... something like we have now with PyPRP.

Taken from the meeting chatlog:

<Lontahv>:When Fan-Created-Ages are allowed will you "legalize" pyprp... if you know what I mean. Because I've grown very used to Blender and comfortable with adding features to PyPrp and would like to continue.

<Chogon>:Yes. PyPrp will be one of the tools. When the source for the plugin get released then the authors of PyPrp can modify it to include more things.

So has the plugin been released yet or not? If so, how do I get it?
Is GoW going to provide tutorials to use 3ds Max?
I have an educational license from Autodesk for 3ds Max as I am a teacher. Can I use that to write ages?

No, the plugin has not been released yet.

I'm not sure if the GoW will ever have as much stuff about the MaxPlugin as about PyPrp (pyprp is this place's identity really) but I'm sure it'll have something after the plugin gets released.

To all you other questions I think I can safely answer: "Dunno, sounds ok."

I don't think Chogon worded the statement the OP quoted the way he meant it. I think that he meant to say the binary for the 3DS plugin would be made available and the source code would be also. I think the "only" refers to the source for only the plugin, not the Plasma engine. I assume we'll get the source so we can adapt the plugin for other modelling tools instead of paying nasally for 3D Studio.

SCGreyWolf wrote:I don't think Chogon worded the statement the OP quoted the way he meant it. I think that he meant to say the binary for the 3DS plugin would be made available and the source code would be also. I think the "only" refers to the source for only the plugin, not the Plasma engine. I assume we'll get the source so we can adapt the plugin for other modelling tools instead of paying nasally for 3D Studio.

That's correct.
They'll split plugin from game-engine before opening up the source.

My only problem is that reading source code, however heavily commented, just isn't the same as reading specs.
I would love to have an up-to-date definition of all prp objects such as the old one that's on the Alcugs wiki.

Chacal wrote:My only problem is that reading source code, however heavily commented, just isn't the same as reading specs.

That's assuming Cyan even has formal documentation of specs for an engine that has changed and grown organically over many years. If they don't already have an up-to-date set of such hypothetical specs, it seems unlikely they'd go to making them now, especially since several of the main contributors to the system over the years are no longer employees.

The plugin, as descriptive rather than proscriptive as it may be, will probably be the best we can hope for as to "formal" specs.

With the release of the plugin, we should verify with Cyan that we can create a spec from the plugin source code. If we can, that would not only aid in the creation of other plugins, but allow others to help with GoW_PyPRP and the other Uru tools.

PaladinOfKaos wrote:With the release of the plugin, we should verify with Cyan that we can create a spec from the plugin source code.

I had assumed this was exactly the reason they're supplying the plugin, but I suppose it wouldn't hurt to double-check that this is their intent.