Who's the host?

BYOND Forums

Announcements · BYOND Help · Bug Reports · Feature Requests · Beta Testers · Beta Bugs · Developer Help · Design Philosophy · Demos & Libraries · Tutorials & Snippets · Art & Sound · Classified Ads · Game Updates · Contests & Events · Linux Talk · On Topic · Off Topic

Who's the host?

ID:273615 Oct 16 2010, 10:18 am
Ryu-Kazuki	Since my last problem was solved. I've run into another. How can I get the game to clarify who's hosting the .dmb from their dream daemon? That way I can do things like give the host certain verbs, or other things.

Oct 16 2010, 11:16 am
Loduwijk	[link] Read that entire thread and you will have exactly what you want.

Oct 16 2010, 2:28 pm In response to Loduwijk
Ryu-Kazuki	I'm confused and still having trouble how to define certain verbs to the host. I went in the reference and searched host and it really didn't help me understand it much.

Oct 16 2010, 4:19 pm In response to Ryu-Kazuki
Gooseheaded	`if(client.address)` If a `client` does not have a `client.address`, it's the host. As simple as that, matey.

Oct 16 2010, 4:57 pm

In response to Gooseheaded

Destroy

Gooseheaded wrote:

if(client.address)

If a client does not have a client.address, it's the host.

As simple as that, matey.

Not quite. Anything hosted in Dream Daemon will give the host an address -- usually "127.0.0.1", but it could be also be world.address or anything random if they're not logging in from the hosting computer. This is why the world.host variable exists, even though that doesn't work with non-Windows hosts.

Typically for giving people verbs you define the verbs in some unused /mob type (like /mob/Host/verb) then add them to the person's verb list on login.

mob/host/verb/Host_Verb()
  src << "You're the host!"

mob/Login()
  ..()
  if(key == world.host || client.address == "127.0.0.1" || client.address == world.address)
    verbs += typesof(/mob/host/verb)

Something like that should cover most of the basic possibilities.

Oct 16 2010, 5:10 pm In response to Destroy
Ryu-Kazuki	Thanks guys, I got it working.

Oct 16 2010, 5:53 pm In response to Destroy
OrangeWeapons	Except, calling ..() before you finish what you wish to do would let Login() continue with what it normally does, and skip the following code, right? I'm not 100% sure, but I think the ..() should be .=..() .

Oct 16 2010, 6:05 pm

In response to OrangeWeapons

Destroy

Either way it'd do the normal login stuff, and Login() doesn't have a return value so . = ..() is pointless.

Usually it's just something I'll normally do -- for 'initialization' procs like New() and Login() the first thing I'll do is call ..() just so that if anything higher up in the call chain has to do anything important it gets done.

Calling ..() never causes code to be entirely skipped, although it might end up sitting around doing stuff if it causes an infinite loop for some reason. (So don't do infinite loops directly in normally overridden procs, spawn() off another proc for those.)

Oct 16 2010, 6:36 pm In response to OrangeWeapons
Garthor	..() doesn't skip anything. .=..() simply stores the return value of ..() in . which is the default return value. It's simply used for procedures such as Move() where there is a return value that you wish to preserve.