Guild of Writers

Hey, has something changed since the Alcugs tutorial about adding Pages to your Age? I'm following it just fine, but I keep getting an error when I go to export. Specifically the error in the console says:

ValueError: invalid literal for int() with base 10: 'xPage'

xPage is what I'm calling the additional page. I made sure to increase the interger from 0 to 1, type and hide are 0 and the Name is xPage.

I've tried changing it to other names but still get the same error.

EDIT: Nevermind! Just me and my bad eyesight again! I was typeing in somehthing wrong. It exported just fine now.

Hey, i'm just trying something out and have a problem.

I have my main stuff, that is in MainRoom.prp
And I have some other stuff that I want to interact with on another Page eg page_num 2
The script isn't seeing these other scenes as pages, what is the process now when dealing with scenes instead of the boxes years ago?

Blender scenes are only used for Importing as pages IIRC. I don't think they're used for exporting at the present even though the plan is to use them for PyPRP2.0 but make some stuff so you can see all the pages at once (Blender has no feature like this for scenes).

So if you guys are trying to import something and then export it unchanged with PyPRP... give up.

Also in Plasma there is usually no interaction between pages but you might have been talking about something else...

For interaction between pages you can use the full name reference in your alcscript. I still would not recommend it though.

Interactions between pages is found quite often in Uru, but confined for, the most part, to GUI's, where the dialog itself is on its own PRP file. The interaction being generally limited to pythonfilemod's that call upon the GUI dialog. The KI, Nexus, and generally every GUI Dialog in the game makes use of this function.

GUIs are rather an exception. The GUI-in-separate-prp thing is so rooted in the engine that Paradox had a hard time getting his GUIs in his shell prp. I forgot exactly how he loaded them eventually.

GPN... I'm getting the feeling you've been soaking your brain in too many GUIs recently.

This is the kind of post I post when I'm looking for the wiki so I can continue work on my RAD entry and get distracted.

Lontahv wrote:GUIs are rather an exception. The GUI-in-separate-prp thing is so rooted in the engine that Paradox had a hard time getting his GUIs in his shell prp. I forgot exactly how he loaded them eventually.

GPN... I'm getting the feeling you've been soaking your brain in too many GUIs recently.

This is the kind of post I post when I'm looking for the wiki so I can continue work on my RAD entry and get distracted.

And I was doing just that when I posted that post

Yes I have been soaking way too much in GUI's. Getting the KI functioning like it did in MOUL is not an easy task. (But I got the jalakcontrolpanel working, so that's a plus.

What I'd really like to do, after RAD is over, is develop an age that utilizes a brand new GUI activated by the KI (like Jalak's is) But that would require to much work on changing the KIMini's dialog, and the KIBlackBar's pythonfilemod. It couldn't be used by anyone who didn't have these functions.

However...a GUI...independent of the KI, thats another ball of was all together.

Lontahv wrote:Blender scenes are only used for Importing as pages IIRC. I don't think they're used for exporting at the present even though the plan is to use them for PyPRP2.0 but make some stuff so you can see all the pages at once (Blender has no feature like this for scenes).

So if you guys are trying to import something and then export it unchanged with PyPRP... give up.

Also in Plasma there is usually no interaction between pages but you might have been talking about something else...

Great thanks for that.

Blender does have that feature where you can pull stuff over to another scene, and from reading the API, it'd be quite possible to implement it to PyPrp.

Well the US has a new president, we New Zealander's go to the polls day after tomorrow

No rush to put any new feature into PyPrp, it was just a general inquiry to know if it can be handled at export, clearly it can't.


I'm quite interested to know how to get PyPrp2.0 to work, seeing as its done in C++, but thats for after the contest, and I know how easy it is to be distracted for several days.