World: r3wp

brb

the same .exe size. The same version, the same behaviour, no logging 
...

start 29-Dec-2009/1:25:05+1:00 ["vertuzo" 5401 1.2.13 29-Dec-2009/1:25:05+1:00]

checking...

Let me upload a .18 version for you to try.

ok ....

www.altme.com/download/altme-18beta.exe

stop all altme and servers, then install that new one.

start 29-Dec-2009/1:36:39+1:00 ["vertuzo" 5401 1.2.18 29-Dec-2009/1:36:39+1:00]

still no detailed debug info ...

verify that log.txt is from altme/servers/vertuzo

yes, the same location as debug file itself ...

I will delete the log

still the same:

halt 29-Dec-2009/1:40:49+1:00 ["halted"]

start 29-Dec-2009/1:40:54+1:00 ["vertuzo" 5401 1.2.18 29-Dec-2009/1:40:54+1:00]

at least the version number is now 18

yes... but I am concerned because I started a new world here to confirm 
the debug settings, and it worked.

what shows in the vertuzo/debug file?

above content, only two lines - I deled it ....

also, how do you start the world?  (from an AltME or from an icon?)

debub file:

; AltME Debugging and Logging Options
debug: 0
file: %log.txt
events: [boot error note start halt wns wns-ping]
echo: none
net: none
time: none

I start it from Total Commander, running altme-vertuzo.cmd:

start altme.exe -s "Vertuzo" -p 5401

try starting it from the altme "Start a World" panel

start 29-Dec-2009/1:49:19+1:00 ["vertuzo" 5401 1.2.18 29-Dec-2009/1:49:19+1:00]
wns 29-Dec-2009/1:49:19+1:00 ["open" "vertuzo" 5401]
wns 29-Dec-2009/1:49:20+1:00 ["close" "vertuzo" lookup ok]

ping success!

command 28-Dec-2009/16:49:20-8:00 [193.85.151.2 {cmd: open data: 
["vertuzo" 0]}]

command 28-Dec-2009/16:50:27-8:00 [193.85.151.2 {cmd: live data: 
["vertuzo" 64#{kDj

hmm ....

so should I not start it via "start"? That sounds strange ... will 
turn the world off, and once again with old method ...

I think this was designed to sell AltServe products.

designed
? :-)

Safeworlds did not want to see people using or reselling AltME free 
product as a server. So, it does not initialize properly when used 
that way.

ok, I restarted it "the old way". I wanted to have it in .cmd, to 
auto-start servers, when machine reboots ...

It's a feature .. not a bug

LOL

Yes.

yes, but it contradicts docs.

I think the docs indicate script startup of free clients, not "free" 
servers.

Docs state, that world, if not used for 10 days, is freed. But it 
is not the case. The world is randomly freed even during its usage. 
The service is unreliable this way ...

Ok, I will bring up this problem and it can be discussed.

I think the big problem is that for users it creates a mystery problem, 
that just looks bad.

You must start your world at least every 10 days (or keep it running 
all the time), or you will lose your world name. If that happens, 
nobody will be able to connect to your world, and someone else can 
take your world name. You can keep your world safe for a small fee.

hmm, so now I understand it. I have to restart world at least once 
in 10 days, or it might loose registration? But my condition of "keep 
it running all the time" is met.

Yes, and that statement is true -- when world is started from AltME 
control panel.

The question now is, why doesn't it "ping", when started from .cmd

Ah... I know.

oh my ... what a logic. If I knew it, I would either buy world names, 
or just run it the manual way. It surely was not obvious to me, but 
imo is not obvious to most users too ...

When running AltME with -s, it runs like AltServe.... which never 
has to ping, because all AltServe worlds have permanently registered 
names.

I think that then docs should be corrected - few sentences would 
explain it clearly enough ...

So... very interesting. At least now we know the source of the problem..

Yes, docs must be updated.

so paying the sum fixes it ...

2:00 am here ... now before I go to sleep, I need some good news, 
e.g. when: host kit will allow View (merge of DELECT and commands), 
Extensions will allow Devices / Callbacks, and when are we back to 
VID? :-) - so that we can start porting R3 to WM and Android :-)