Posts by Absalom

I use the arrow keys to rotate.

Thanks for spending your Saturday on this. Must be frustrating.

I finally got connected to my test server after many many many tries. win.thedeadlands.net:30700. But still cannot get connected to my main server: win.thedeadlands.net:30500. Both were updated exactly the same.

I reported it under technical->client problems

Nope definitely can't connect. Here's the server log if it helps at all.

I see other players connecting in the server log, so I am going to try removing my client and reinstall.

I get a connection error every time since the update a few minutes ago. Though I can see my server in the list. I have attached my info file.I would report this in the bug tracker, but when I attempt to go there, it says the bug tracker doesn't exist.

I notice that sometimes my I lose control of my area. I usually have to add myself as owner again. Until I have fully extended the AreaProtection, if that happens to you, let me know and I will add you back to your area.

I am having trouble understanding how addEvent is supposed to work. Given the following example:

[lua]addEvent("eventName", listenerFunction1);
addEvent("eventName", listenerFunction2);[/lua]

I would expect listenerFunction1 and listenerFunction2 to listen to the same event "eventName". However, it seems only one or the other can be added as a listener. This makes scripting separate command handlers impossible. For example, I have:

[lua]
function motdCommands(event)
-- some code here
end
addEvent("PlayerCommand", motdCommands);
[/lua]

[lua]
function areaProtectCommands(event)
-- some code here
end
addEvent("PlayerCommand", areaProtectCommands);
[/lua]

I would have expected both of these functions to have registered as listeners of the PlayerCommand event. But only one of them listens to that event. Am I wrong? Both were reported to have registered successfully in the console output.

Each time the server hangs, whether it doesn't load the terrain, causes players to not be able to interact with the world, or causes a connection error, I always see this type of error spammed a LOT in the log: "Dec 12, 2014 10:31:46 PM t.d a
WARNING: PlayerConnect: NpcInitSpawn remaining bytes smaller than required bytes" And this one: SEVERE: Fatal error occured:
Dec 12, 2014 10:04:35 PM server.Main handleError
SEVERE:

Direct Memory:

There isn't any real useful information in the log at all.

Restarted. It seems the more and more people we get connecting, the more and more it needs to be restarted.

Thanks. My other buddy, Casper, passed away a few months ago. She's been pretty inactive (probably depressed) since he died. It was very sad. Here's Caspers last few days: https://www.dropbox.com/s/4bt4…/20140728_105312.mp4?dl=0
https://www.dropbox.com/s/y6c1…/20140728_125313.mp4?dl=0

China and her new obsession.https://www.dropbox.com/s/edpa…/20141212_163217.mp4?dl=0

https://www.dropbox.com/s/edpa…41212_163217.mp4?dl=0</a>

I saw different type of data in mine. hmm.

You could also run the windows client under wine. I believe windows java jre runs under wine.

I was going to ask if it was around midnight when it disappeared. And did a number of mice disappear as well? Has there been a carriage pulled by a couple of horses sighted in the area?

Ha! Just kidding. Hope you get it resolved.

I purchased it on the 4th I think. I like it.

Go into your risingworld install directory and take a look at the info file in a text editor. It will have errors pertaining to disconnects.

Quote from Grey

Hi! I just tried playing on your server last night, unfortunately, I am still not able to do anything related to the F key, like pick up or craft or use anything.

Normally, if you are unable to interact with the world, that means that you connected but then got disconnected and are playing only on the cient side, in sort of a cached world. Obviously all rendering happens on the client, but when you are disconnected from the server, there is nowhere to send your updated info and I assume that is why things stop interacting when you hit F.

Firedaemon pro apparently appends to the log. So it is about 350 MB. I will look at it later to see what was going on. I saw an exception with a socket connection at some point, but I doubt that would have affected the server terrain loading. The AreaProtection is spamming in most of the log. lol. I know it isn't that though because this happened before the AreaProtection was in place...if I remember correctly.