VGOEmulator.net

For our current list of "GM Commands", I found a workaround today. Thought I'd share. In New Telon, we have the global chat channel on channel 3 by default. When you talk there, /3 becomes the default channel. A bug in the (new) chat code doesn't seem to listen for .commands on that channel.

So you have to type /say .command {blah}

Eg.,
/say .speed 3000
/say .rift 1
/say .move -50000 -12000 24800 (a spot Mithnl and I just discovered in IslandofGaruzamut

Just to clarify, all channels listen for commands all the time. This issue is caused by the world client disconnecting which gives the appearance of commands/chat not working. That issue is caused by the fact there is very little keep alive activity the client sends to world on the world connection. I opted to manually update world client heartbeats based on chunk client heartbeats to get around this issue.

A side effect from this is I can now lower the timeout of client connections so reconnecting shouldn't be as big of a problem.

Yeah, seen the commands work on global chat, that and with no abilities, I just have lots of macros for commands.

[quote="theFoof"]A side effect from this is I can now lower the timeout of client connections so reconnecting shouldn't be as big of a problem.[/quote]
Foof, was this lowered timer that UDP timer (40s to 10s) that effected Logins?

I'm still getting all my commands to work after switching my channel default back to /say (local channel) when they definitely do not work if I'm defaulted to NewTelon (world channel). I understand the disconnect thing, but this workaround, works. Though I think a ton of issues would get cleared up once the disconnect problem is resolved.

[quote="John Adams"][quote="theFoof"]A side effect from this is I can now lower the timeout of client connections so reconnecting shouldn't be as big of a problem.[/quote]
Foof, was this lowered timer that UDP timer (40s to 10s) that effected Logins?

I'm still getting all my commands to work after switching my channel default back to /say (local channel) when they definitely do not work if I'm defaulted to NewTelon (world channel). I understand the disconnect thing, but this workaround, works. Though I think a ton of issues would get cleared up once the disconnect problem is resolved.[/quote]
I sometimes have an issue with the .speed command not working in /say or global. Usually rifting fixes it.

[quote="Cyrcle"][quote="John Adams"][quote="theFoof"]A side effect from this is I can now lower the timeout of client connections so reconnecting shouldn't be as big of a problem.[/quote]
Foof, was this lowered timer that UDP timer (40s to 10s) that effected Logins?

I'm still getting all my commands to work after switching my channel default back to /say (local channel) when they definitely do not work if I'm defaulted to NewTelon (world channel). I understand the disconnect thing, but this workaround, works. Though I think a ton of issues would get cleared up once the disconnect problem is resolved.[/quote]
I sometimes have an issue with the .speed command not working in /say or global. Usually rifting fixes it.[/quote]


I was having this issue tonight with speed not working, I .rifted around and still couldn't get it to work for me.

I was trying:

.speed 1000
/say .speed 1000
.speed {1000}
/say .speed {1000}

As I wasn't sure which one was the correct command but in the end, none of them worked for me.

How I get it to work is to type /say

enter. so the channel is now defaulted to Say:

Then, type the .speed 3000 command

If I am on /3 NewTelon, it would not work after a certain length of time. And overriding it with /say .speed did not work.

I've seen a few people mention after you chunk sometimes it stops working, it's likely an unreal packet thing rather than the actual command in those cases. If your world chat is still working then it's the latter.

[quote="John Adams"]How I get it to work is to type /say

enter. so the channel is now defaulted to Say:

Then, type the .speed 3000 command

If I am on /3 NewTelon, it would not work after a certain length of time. And overriding it with /say .speed did not work.[/quote]

Thanks mate, I was doing it wrong then.

[quote="theFoof"]I've seen a few people mention after you chunk sometimes it stops working, it's likely an unreal packet thing rather than the actual command in those cases. If your world chat is still working then it's the latter.[/quote]

It sometimes doesn't work when you use the .rift command. However when I ran across a chunk line it always kept the speed I had in the last chunk. Even when I ran across half a continent.