Guild of Writers

Hi:
I have decided to do some CWE development using the GoW fork. I have gotten DirtSand installed and have decided to use a "Minimalistic Development Shard" approach following this gide at "http://www.guildofwriters.org/wiki/Minimalistic_Development_Shard", however when I try and connect the client I built, I get this invisible error when loading at the book screen:
"---------------------------
Microsoft Visual C++ Debug Library
---------------------------
Debug Assertion Failed!

Program: ...sers\Marchant\source\MOULa\Plasma\bins\bin\Debug\plClient.exe
File: C:\Users\Marchant\source\MOULa\Plasma\Sources\Plasma\FeatureLib\pfSecurePreloader\pfSecurePreloader.cpp
Line: 110

Expression: SecurePreloader manifest empty!

For information on how your program can cause an assertion
failure, see the Visual C++ documentation on asserts.

(Press Retry to debug the application)
---------------------------
Abort Retry Ignore
---------------------------
"
Followed by:
"
---------------------------
UruLive Error
---------------------------
Secure file preloader failed
---------------------------
OK
---------------------------
"
I was wondering how I move past this, thank you.


If this is in the wrong spot could you please tell me and move it to the correct spot. Thank you.

I have thought of a way to solve this, put security files on my sever for my client to download. I only must remember which files they are to replace them on the server if I change them(I'm not planning on working on the Python so this will lickly not be a problem). What files do I need to put in the manifest/on the server to make this possible?

For local testing, you should just drop the Python and SDL directories into the client directory, then launch plClient.exe with the /LocalData switch.

Of course, if you're going to run a real shard, you'll want those secure preloader manifests available

Uh thank you

This looks like an appropriate place to post a little cry of help.

I finally got my Linux system up and all the proper software loaded to build the minimalistic Development shard (Dirtsand). After some head scratching and head banging I finally got cmake to agree I had all the correct header and lib files installed when the make generated about 4 errors that appear to be from semaphore.h.

Did I miss something about configuring threads or something? IIRC it was all unreferenced statements (sem_init() and his friends) in MsgChannel.cpp. There were a number of other warnings generated in other modules. I can probably remember how to redirect the output messages in a file if you would care to look at it.

Edit: NVM. I was forced to rebuild the system due to a stupid configuration error and everything compiled fine. Who'd a thunk?

Edit2: Never a dull moment... Apparently in 9.1 you have to use CREATE EXTENSION to implement the uuid function in the DB... I think I had it right but forgot the stupid semicolon at the end of the line. Will try again tomorrow.

OK. I managed to figure it out.

To add the extension functions in uuid-ossp in Postgre 9.1, the procedure is a bit different (and much simpler).

Code: Select all

sudo -u postgres psql -d dirtsand
psql (9.1.3)
Type "help" for help.

dirtsand=# CREATE EXTENSION "uuid-ossp";
dirtsand=# \q

Had to change CREATE LANGUAGE plpgsql in functions.sql to CREATE OR REPLACE LANGUAGE ... to get it to run without error in Postgre 9.1.3.

I managed to get dirtsand to run but I had a question about the keys... keygen new gave me all the keys for dirtsand.ini but I wasn't sure if I should include the quote marks in the INI file. None of the other values in there are quoted.

Edit: still messing around with this. I have only one more problem (so far) I can't seem to figure out or even find in the code... might be coming from Postgre...

Error connecting to postgres: fe_sendauth: no password supplied

I put the data in the INI file but it doesn't seem to work. I have no problem connecting to the DB with psql or pgadmin.

OK. It came from outer sp.... ah libpq-fe.h

Code: Select all

/* Error when no password was given. */
/* Note: depending on this is deprecated; use PQconnectionNeedsPassword(). */
#define PQnoPasswordSupplied    "fe_sendauth: no password supplied\n"

Since I did supply a password, is there any idea what exactly I may have done wrong? Nothing will work if I can't connect to the DB.

NVM: I figured it out without any help... thanks anyway.

I have an internal client build (it even starts!). I have a dirtsand server... it appears to be running as well. However, the two do not seem to talk to each other. Since no one seems to have been interested in responding to my previous posts, I've been forced to figure most things out for myself (yeah, great learning experience ).

I think I've tracked down the problem to my server not listening to the outside world. I rattled some ancient Unix memories and think I need to enable some ports but I'm not sure of which ones and the proper settings for them. For now I just need to have a minimalistic devel shard setup. Any guidance on setting up the necessary ports? (/me begs)

DS runs on port 14617 iirc look in the dirtsand.ini it is in there

What does your server.ini look like? Is there a firewall between the server and the computer that is trying to connect?

To be honest, it seemed like you were figuring it out on yourself. Also you'll get more and faster help if you join the IRC channel, #writers on irc.justirc.net

Thanks. My INI is fine. The port is simply not enabled to listen external to the box. This is all on my internal home network so the only firewall would be on the linux box. I'm not sure if there is a firewall running on the box but mostly all the ports were off by default. I'm just struggling to dig through the documentation to figure out what to do. 20 years ago, I would have just edited a certain file and rebooted. The state-of-the-art seems to have moved on a bit since then. I think the key is in iptables. What we need is an article on setting up your dirtsand system and software for the compleat dummy who doesn't have a clue and should know better than to try.