diff options
| author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
| commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
| tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2000-November/000039.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to 'pipermail/nel/2000-November/000039.html')
| -rw-r--r-- | pipermail/nel/2000-November/000039.html | 73 |
1 files changed, 73 insertions, 0 deletions
diff --git a/pipermail/nel/2000-November/000039.html b/pipermail/nel/2000-November/000039.html new file mode 100644 index 00000000..f76ffc30 --- /dev/null +++ b/pipermail/nel/2000-November/000039.html @@ -0,0 +1,73 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] Some thoughts about NeL</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:archer%40nevrax.com"> + <LINK REL="Previous" HREF="000038.html"> + <LINK REL="Next" HREF="000042.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] Some thoughts about NeL</H1> + <B>Vincent Archer</B> + <A HREF="mailto:archer%40nevrax.com" + TITLE="[Nel] Some thoughts about NeL">archer@nevrax.com</A><BR> + <I>Wed, 15 Nov 2000 17:27:27 +0100</I> + <P><UL> + <LI> Previous message: <A HREF="000038.html">[Nel] Some thoughts about NeL</A></li> + <LI> Next message: <A HREF="000042.html">[Nel] Problems ?</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#39">[ date ]</a> + <a href="thread.html#39">[ thread ]</a> + <a href="subject.html#39">[ subject ]</a> + <a href="author.html#39">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>According to Thierry Mallard: +><i> This is something I though about in the Genesis project (yes I know, +</I>><i> not very original name ;-) a few years ago. The problems we found +</I>><i> were the consistency of the global universe, and the trust we could +</I>><i> have to any server. For example : who managed the characters ? who +</I>><i> can we trust for them ? There can be a time line synchronisation problem +</I>><i> too, although that seemed less important... +</I> +In a very different world (and a closed system implementation), it's also +something Bioware's NeverWinterNights wants to achieve. Their model allows +servers (what they call modules, which is in fact a process running a +specific area - but you can have multiples instances concurrently running +on the same CPU) to link to each other. + +Of course, their model is simpler: all servers are guaranteed to run the +same software (it autoupdates over the Internet), the character formats are +well defined, and the characters are ultimately stored on a central database +(the NWN Vault) who enforces "plausibility" on the characters (a level 1 +cannot get to level 6 and 70,000 XP points in an hour of playtime; a level 3 +character cannot have a plate+2, a cloak of displacement and boots of speed, +and so on). + +And they do not want to inforce any universe continuity: each server admin +has to do it, by allowing other modules to link to yours or not. +-- +Vincent Archer Email: <A HREF="mailto:archer@nevrax.com">archer@nevrax.com</A> + +Nevrax France. Off on the yellow brick road we go! + +</pre> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000038.html">[Nel] Some thoughts about NeL</A></li> + <LI> Next message: <A HREF="000042.html">[Nel] Problems ?</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#39">[ date ]</a> + <a href="thread.html#39">[ thread ]</a> + <a href="subject.html#39">[ subject ]</a> + <a href="author.html#39">[ author ]</a> + </LI> + </UL> +</body></html> |