<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="zh">
	<id>https://game.etao.net/w/index.php?action=history&amp;feed=atom&amp;title=Client_Object</id>
	<title>Client Object - 版本历史</title>
	<link rel="self" type="application/atom+xml" href="https://game.etao.net/w/index.php?action=history&amp;feed=atom&amp;title=Client_Object"/>
	<link rel="alternate" type="text/html" href="https://game.etao.net/w/index.php?title=Client_Object&amp;action=history"/>
	<updated>2026-05-05T16:51:52Z</updated>
	<subtitle>本wiki上该页面的版本历史</subtitle>
	<generator>MediaWiki 1.43.0</generator>
	<entry>
		<id>https://game.etao.net/w/index.php?title=Client_Object&amp;diff=151&amp;oldid=prev</id>
		<title>imported&gt;Wkadmin：​导入1个版本</title>
		<link rel="alternate" type="text/html" href="https://game.etao.net/w/index.php?title=Client_Object&amp;diff=151&amp;oldid=prev"/>
		<updated>2020-04-21T09:20:57Z</updated>

		<summary type="html">&lt;p&gt;导入1个版本&lt;/p&gt;
&lt;p&gt;&lt;b&gt;新页面&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{Navigation for Marauroa Top|Internals}}&lt;br /&gt;
{{Navigation for Marauroa Developers}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Future Concept}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Proposal ==&lt;br /&gt;
*Instead of having custom client objects in a per application basis define one that can be enhanced via plugins.&lt;br /&gt;
*Specify Client Object implementation on ini file&lt;br /&gt;
&lt;br /&gt;
== Reason ==&lt;br /&gt;
*Not all applications need existing attributes like x and y&lt;br /&gt;
**Those should be handled via plugins&lt;br /&gt;
*Standardize approach&lt;br /&gt;
&lt;br /&gt;
== Example Implementation ==&lt;br /&gt;
[http://simple-marauroa.svn.sourceforge.net/viewvc/simple-marauroa/trunk/Simple-Server/src/simple/server/core/entity/clientobject/ClientObject.java?revision=101&amp;amp;view=markup Client Object]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Discussion ==&lt;br /&gt;
&lt;br /&gt;
I am strongly opposing putting such game specific attributes and logic into Marauroa. It might be a good idea to create a set of libraries that can help developing certain types of games by providing functionality that is typically used by a game of the respective type. But Marauroa should focus on client/server communication and database persistence. Marauroa does not even know about x and y as your wrongly claimed although most games have coordinates. So adding even more things such as grumpy, buddies, ignore in your code is out of scope for Marauroa.  --[[User:Hendrik Brummermann|Hendrik Brummermann]] 18:07, 14 May 2011 (CEST)&lt;br /&gt;
&lt;br /&gt;
I&amp;#039;m not saying that my example is the way to go, I&amp;#039;m saying it should be extensible enough. I use interfaces and define the client object at runtime loading by reflections like other objects are (i.e. world implementation). The same should be available for the client object.--[[User:Javydreamercsw|Javydreamercsw]] 22:17, 27 September 2011 (CEST)&lt;/div&gt;</summary>
		<author><name>imported&gt;Wkadmin</name></author>
	</entry>
</feed>