Why COH will not get a server emulator.

[Profit]

Code: [Select]

2. Profit!

Yes?

[Kyriani]

Frankly, yes.  I did like the i23 version of the game, and so, if I were 'stuck' with that, I'd be ecstatic..I will happily admit, I do want to see i24, too...   But I dont think an i23 version would be 'settling'..  And I totally disagree with.. "And that's not what we want".  I want CoH back, period...  I will take that. If it is ever offered...


But, I have to commend ya on all the technical details


Cheers

I think his intention in that post wasn't so much saying "we don't want a frozen at i23 or i24 COH" but rather I think he was saying "Why settle for i23/i24 that never advances when we can have endless expansion possibilities on top of i24"

[Starsman]

[Codewalker]

It's also partly a connotation issue. As someone who has played some other MMOs and seen the various developments going on, there are two things that are typically called "emulators" by the communities of those games:

• A private server that is either based directly on leaked code (Aion), or written to interface with leaked server data files (WoW), both of which are extremely dubious and much more likely to be subject to serious legal action than a clean implementation.
  
  
• A half done hack job running on a crappy MySQL database that barely works, crashes all the time, and is so buggy as to not really be playable. Often missing pretty much all content other than whatever monsters the server admins feel like spawning for giggles, which probably don't even have working AI.

There are a few notable exceptions (SWGEmu comes to mind), but they're rare.

We don't want either of those.

[The Fifth Horseman]

Correct me if I'm wrong here: does this mean that
1) from the point of view of a player that never touches or administers either server (original official one or the compatibility one) there is no distinction, he just see what he can honestly call "emulation"
2) From the point of view of an admin, or developer that works on or administers the server, there will be a very obvious difference and (should he know the definition of emulation as you stated before) he will never dare call it emulation (or accept anyone else calling it so.)

Sounds about correct.

[Starsman]

There are a few notable exceptions (SWGEmu comes to mind), but they're rare.

SWGEmu is already functional?

[Numerology]

SWGEmu is already functional?

Looking back over their news archive they have had players on the test server from at least 2010. I don't recall when they launched their proper live servers or know how many features are still to be fully developed however.

[Arcana]

[Arcana]

It's also partly a connotation issue. As someone who has played some other MMOs and seen the various developments going on, there are two things that are typically called "emulators" by the communities of those games:

• A private server that is either based directly on leaked code (Aion), or written to interface with leaked server data files (WoW), both of which are extremely dubious and much more likely to be subject to serious legal action than a clean implementation.
  
  
• A half done hack job running on a crappy MySQL database that barely works, crashes all the time, and is so buggy as to not really be playable. Often missing pretty much all content other than whatever monsters the server admins feel like spawning for giggles, which probably don't even have working AI.

There are a few notable exceptions (SWGEmu comes to mind), but they're rare.

We don't want either of those.

Which is why I really consider all community server projects I'm aware of reimplementations.

[Starsman]

[Arcana]

[redgiant]

In a casual conversation about server replacements for CoH, I wouldn't nit-pick the use of the term "server emulator."  But this was a discussion about the specifics, and that casual immunity no longer applies here.

You are by definition emulating the communications protocol between client and server no matter what use of the client you are making.

What you may or may not be additionally emulating are the game content and systems, such as what maps and mobs it uses, and all the behavior and calculation results that sum up to act and look like "The Game" we played before.

1. If experiencing Atlas Park or any familiar map play as close to Nov 30, 2012 as possible, then you are attempting to emulate City of Heroes content-wise as well.

2. If not, and you just want to use the client but show a different landscape or one that behaves differently in small or large ways, then you are only emulating some of the gameplay component systems enough to do that job.

Clearly (1) requires much more detailed replacement gameplay systems server-side to try to respond to the client in as much the same way the real Servers would have that is possible. Everything from combat mechanics and calcs to scripted events have a big burden on them to result in the same communications stream as the real Servers would have produced, regardless of what spinning gerbils in your black box are used to accomplish that.

All (2) requires is that the messages to the client make sense. Without the goal of emulating the content and gameplay systems we knew, this could result in an infinite variety of games that have anywhere from some passing resemblance to CoH, to looking more like WoW or Everquest ifyou so chose.

So its all in the level of emulation desired by you.

---------------
tl;dr

Communications protocol emulation is required no matter what.

Content and gameplay systems behavior emulation is only needed to the extent you are trying to copy the old City of Heroes content and behavior we knew. Without this goal, you could drive the client as a game that looks and acts nothing (or partially) like what we knew.

So it is an emulator by definition. The extent of emulation is the only question.

[Arcana]

You are by definition emulating the communications protocol between client and server no matter what use of the client you are making.

To be precise, you can emulate a system that uses a protocol, but not literally emulate a protocol (which I imprecisely stated colloquially earlier).  Something that "emulates" a protocol and something that implements a protocol are indistinguishable from each other.  Emulation by definition reproduces behavior, not structure, in operational definitions involving software.

No definition of emulation I consider reasonably valid for software systems would imply that implementing a communications protocol was a form of emulation.  In a professional context, I would consider someone trying to convince me its possible to functionally emulate HTTP without implementing HTTP to be high.

[Mister Bison]

To be precise, you can emulate a system that uses a protocol, but not literally emulate a protocol (which I imprecisely stated colloquially earlier).  Something that "emulates" a protocol and something that implements a protocol are indistinguishable from each other.

I think I can think of some protocols out there that "emulate" another protocol. At least new versions of old protocols are this when they want to be retrocompatible. Like the ISO model can easily emulate the TCP/IP model (okay that's not a protocol but you get the point). And isn't USB2 this to USB1.1 ? (there is no need for two hardwares to make devices compatible to the two protocols)

[candidate]

I remember reading similar post as OP in some WOW forums, saying why wow players would never see an emulator.

6 months later I was able to play on a private server.

So anything is possible.

But ofc a LEGAL private server will never be.

[Septipheran]

lol, is this whole thread about whether or not it's okay to call a generic company's tissue a kleenex instead of a tissue? Personally I just want to blow my nose, man.

[Arcana]

I think I can think of some protocols out there that "emulate" another protocol. At least new versions of old protocols are this when they want to be retrocompatible. Like the ISO model can easily emulate the TCP/IP model (okay that's not a protocol but you get the point). And isn't USB2 this to USB1.1 ? (there is no need for two hardwares to make devices compatible to the two protocols)

USB2 is backward-compatible with USB1.1.  USB2 specifies that all USB2 devices must support the requirements of USB1 and negotiate them appropriately.  To put it another way, USB2 is a superset of USB1; it includes as a requirement the exact communications protocol of USB1.  It does not emulate USB1.  A USB2 device could perhaps be described as being able to emulate the behavior of a USB1 device, but USB2 does not emulate USB1.  It implements USB1 directly as a requirement of the specification.

The closest thing I can think of to "protocol emulation" are network testing systems.  There are systems that pretend to execute a network protocol to test that all the transmission equipment handle that transmission correctly.  I use VOIP testers, for example, that generate something that appears to be SIP call traffic from one end of a network to another.  These are often colloquially called "protocol emulators" in that they appear to implement SIP or H.323 but don't really: the two end points are talking gibberish and not really even listening to what each other is saying except for the minimum necessary to keep things like session state and round-trip lag elements of the protocol valid. 

In a sense its a form of "protocol emulation" in that its reproducing the behavior of a system relative to some standard (that standard being what intermediate network gear sees) but its not really emulating the protocol itself; its emulating the network characteristics of the protocol for test purposes.

[Arcana]

I remember reading similar post as OP in some WOW forums, saying why wow players would never see an emulator.

6 months later I was able to play on a private server.

So anything is possible.

I suspect that one day someone will publicly announce a City of Heroes server emulator.  Its just unlikely it will actually emulate the original CoH servers except superficially.  Not because its impossible, but rather because its technically suboptimal to even try compared to all other reimplementation alternatives.

[Little Green Frog]

I suspect that one day someone will publicly announce a City of Heroes server emulator.  Its just unlikely it will actually emulate the original CoH servers except superficially.  Not because its impossible, but rather because its technically suboptimal to even try compared to all other reimplementation alternatives.

You know, by no definition emulators are required to precisely replicate inner workings of a system they imitate.

[Mister Bison]

USB2 is backward-compatible with USB1.1.  USB2 specifies that all USB2 devices must support the requirements of USB1 and negotiate them appropriately.  To put it another way, USB2 is a superset of USB1; it includes as a requirement the exact communications protocol of USB1.  It does not emulate USB1.  A USB2 device could perhaps be described as being able to emulate the behavior of a USB1 device, but USB2 does not emulate USB1.  It implements USB1 directly as a requirement of the specification.

The closest thing I can think of to "protocol emulation" are network testing systems.  There are systems that pretend to execute a network protocol to test that all the transmission equipment handle that transmission correctly.  I use VOIP testers, for example, that generate something that appears to be SIP call traffic from one end of a network to another.  These are often colloquially called "protocol emulators" in that they appear to implement SIP or H.323 but don't really: the two end points are talking gibberish and not really even listening to what each other is saying except for the minimum necessary to keep things like session state and round-trip lag elements of the protocol valid. 

In a sense its a form of "protocol emulation" in that its reproducing the behavior of a system relative to some standard (that standard being what intermediate network gear sees) but its not really emulating the protocol itself; its emulating the network characteristics of the protocol for test purposes.

If what's bold, that is what you say, is not saying "USB2 protocol requires all devices to comply with protocol USB1", and so, "USB2 protocol incorporates protocol USB1 and more" that is, "USB2 imitates USB1 and exceed it", then I'll be damned.

I'm going to propose the definition in Wikipedia's article on Emulators, which stipulates that "In computing, an emulator is hardware or software or both that duplicates (or emulates) the functions of a first computer system (the guest) in a different second computer system (the host), so that the emulated behavior closely resembles the behavior of the real system. This focus on exact reproduction of behavior is in contrast to some other forms of computer simulation, in which an abstract model of a system is being simulated. For example, a computer simulation of a hurricane or a chemical reaction is not emulation." So, as long as the intent is to provide an exact reproduction of behaviour, of which we have had countless examples an we even know the majority of the rules, then yes, we can have an emulator of City of Heroes, as long as the people who have the best knowledge of it are behind it, and as long as it was a human-created system, it can be recreated to fool every other human as being the real thing.

And I think we've just got the kind of person quoted in this post, the rest of this kind must already be on Titan board, and the kind that can't help us because of NDA shouldn't count.

If the problem is the server's input file being an unknown, that's partially correct. Those are not unknown, they are variables. Emulation doesn't care to emulate every data it's going to have presented, it copies the mechanism. Saying a "community server" can't be an emulator because we will never have the server data files is like saying you can't have homebrew on the PSP because we couldn't read what was on the discs. We all know the data that was in the server files, the only problem being we don't know their format is moot. When you plug an MP3 player on a pair of speakers, they don't care if the format was in fact Ogg. The output is the same. That's the same with CoH client and a community server, wether it's an emulator or a reimplementation is the same - the game is supposed to function the same.

Maybe the cruelest fact would be that the server files are forever gone. So no developer will never have to ever bother with making what would truly be considered an "emulator" because there is nothing to emulate except the whole server and its data altogether. Then isn't that an emulator ? It also transforms raw power into client-compatible data ! We reimplemented all the mechanisms necessary to produce the same output, and it will have the same input: the client commands and raw power.