Poll

New set of feature's name? (read)

BLG Unite
7 (77.8%)
BLG Link
1 (11.1%)
Other (post)
1 (11.1%)

Total Members Voted: 9

Author Topic: BLG (Unite) Development  (Read 46049 times)

Do I have to compile the code and run blocklandglass-server?
Never mind, it's git.
« Last Edit: August 22, 2012, 11:39:23 AM by Pacnet2012² »


It just doesn't work.

 Ran on Windows Server 2008 R2 (You may have to zoom in on the image).


First off, did you fork the repository? Second, why are you trying to pull off a fork? Are you trying to contribute to the project?

And no, Glass-Server isn't needed by you.

It just doesn't work.

 Ran on Windows Server 2008 R2 (You may have to zoom in on the image).

[IMG ]http://i1120.photobucket.com/albums/l489/Pacnet2010/Untitled-13.png[/img ]
I see my name! :D

And no, Glass-Server isn't needed by you.

Apparently I did whatever it said on Git.rtf, and I surely do need Blockland Glass because Ark needs it for his server, and also I need it if my current remote start / stop doesn't get fixed, because it isn't really working out.

I'll investigate Glass server when I get home to see if it's an issue on my end. Make sure you have the alpha zip on the server and not the standard. The server auto-updater isn't in the standard.

I'll investigate Glass server when I get home to see if it's an issue on my end. Make sure you have the alpha zip on the server and not the standard. The server auto-updater isn't in the standard.
After I updated in the client, I put it in the FTP. so Im sure it is alpha.

Apparently I did whatever it said on Git.rtf, and I surely do need Blockland Glass because Ark needs it for his server, and also I need it if my current remote start / stop doesn't get fixed, because it isn't really working out.
git.rtf is for developers. If you don't know how to use git, I don't recommend using it to download BLG for consumer reasons. The wrapper with start/stop wont be ready for some time.

Code: [Select]
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection 372 disconnected
Connection 372 disconnected
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success
Connection from 96.248.119.33
Challenge Success

Note that there are no disconnects. There is also no message saying Blockland authed successfully, leading me to believe that it is related to that. Ill look in to it.

Authentication relies on $Pref::Player::NetName, which is never loaded on a dedicated server if the client has never been run. I'll include a fix for this in A4. For now, just enter $Pref::Player::NetName = "Ark"; in the console and try restarting.
« Last Edit: August 22, 2012, 06:49:30 PM by Scout31 »

I think we found our problem:

~Removed~
« Last Edit: August 22, 2012, 09:05:20 PM by Darkmaster20 »

Nah, I was just now restarting the server for an update that would allow me to debug further. It appears that the name is being received but auth isn't succeeding. I'll investigate.

Nah, I was just now restarting the server for an update that would allow me to debug further. It appears that the name is being received but auth isn't succeeding. I'll investigate.
Okay, Detective Jinxcus

It appears that the name is being received but auth isn't succeeding.