Is there a way...I am using xoops...http://morbidfascinations.com.  I am wondering if there was a way that when they create a user on the website..if they would get a user account in logd?  I am wanting to make the game only availiable to registerd users and have a account made for them when they register on the website?
Thanks

Could write a Xoops module/Modify the Xoops signup script to create the username/password in the LoGD accounts table and then when they logged into LoGD they would be prompted to fill out the rest of their character information.

Which would make it much simpler.

Not necassarily..

If you just did an insert for those 2-3 (If Email is needed) fields then it will prompt you to create your character upon signing in.

Course you would have to do the password encryption, but otherwise it is pretty straight forward.

Actually you are partially correct. I missed one thing. You would have to do a sex insert.

So it would have to have:
username
password
sex

That is all. No reason why it will not work.

I just tried it, since my suggestions based on reading the code don't seem to convince you, and you don't get properly assigned a title, you get no starting gold, you miss the processing of modules that hook process-create, create-form or check-create, you don't get marked as the newest player, and probably other stuff I didn't check for.

None of the code in create.php happens, and most of this code is not duplicated anywhere else. xdebug confirms that at no point during login does create.php get read (which should be obvious).

Processing module hooks in particular would be very hard to duplicate in an XOOPS module.

Reproducing large amounts of the behaviour of create.php, or hacking up bits of core to make login do some complex dance of redirection, is the bit I'd call overcomplicated.. and it makes your app very fragile, and prone to fall over if you, say, were to update logd.

I'm saying it'd be much easier to do it my way, not that it's the only way it can be done. A small change to login to auth against a different table (very small if you didn't care about it being useful to other people, and hardcoded XOOPS's behaviour into it), a small change to create to drop some fields and read the session from the other app (again, smaller if you hardcode XOOPS's behaviour), and you're done. Less work than your typical nasty portal-addon-to-forum-code, no duplicating LotGD code (might manage without duplicating XOOPS code either, if you're lucky and the php files can be included sanely), and all LotGD char-creation related stuff (settings, module hooks, etc) will Just Work(tm).

The solution I propose doesn't require touching a single line of XOOPS code, though you might need to read some of it to understand the session format and the encryption method used for the password. LotGD is the application with the special requirements here - if it were just some forum or something, doing a dual-create would be far more reasonable, as both would require similar user information and would likely not need complex new-user processing. Thus, it seems sensible to leave XOOPS alone, as it's doing what it's good at (being a CMS, and managing users in the normal website fashion).

You could just post the data to "create.php?op=create" after passing it through the md5pass() function. The JS code for it is in the create character page