SoC Ideas Multiplayer server - Revision history

Egallager: link cleanup

2023-04-24T02:22:13Z

link cleanup

Dave: /* Required knowledge and talent */

2009-03-25T18:41:34Z

‎Required knowledge and talent

SkeletonCrew: fix formatting

2009-03-22T09:02:44Z

fix formatting

SkeletonCrew: /* See also */ added some links

2009-03-22T09:02:12Z

‎See also: added some links

SkeletonCrew: /* General Description */ remove the already implemented idea

2009-03-11T19:32:04Z

‎General Description: remove the already implemented idea

Dave: /* General Description */

2009-02-15T19:38:24Z

‎General Description

Ivanovic at 23:03, 18 March 2008

2008-03-18T23:03:04Z

Ivanovic: New page: === Extending the Multiplayer server === Our multiplayer community is generally strong and healthy, but we believe its growth is limited by some problems in the interface of the multiplay...

2008-03-18T14:43:10Z

New page: === Extending the Multiplayer server === Our multiplayer community is generally strong and healthy, but we believe its growth is limited by some problems in the interface of the multiplay...

New page

=== Extending the Multiplayer server ===

Our multiplayer community is generally strong and healthy, but we believe its growth is limited by some problems in the interface of the multiplayer lobby.

==== General Description ====
The general idea of this project would be
* To study the current lobby,
* To develop ideas about how our multiplayer interface could evolve to allow it to scale to a much larger community
* And to implement as many of those changes as practical

Some ideas that we had (but that are in no way mandatory):
* Having a simple way to register and authenticate nicknames, similar to what IRC offers. The point is not to have cryptographically safe logins, but to have something simple that gets the job done
* Having a simple room system? Again, inspired by IRC
* Having some way to find the type of games you are interested in. filtering by:
** game type
** number of free slots/players
** any other criteria you might find interesting

Other ideas we are not yet convinced are good, but that are certainly worth studying (especially how the communities based around these concepts are different from ours)
* ranking players
* guilds
* official tournaments
* titles for players
* metaservers
* game matching when players are ranked (poker, bridge...)

The scalability of the design (both in term of number of players, and in term of the possibility for players and developers to extend the concept) will be an important criterion.

Administration/moderation problems and techniques should also be studied.

Interaction with the Add-On server/forum should be explored.

==== Required knowledge and talent ====

* A fair amount of experience with C++ is required. Wesnoth uses some advanced C++ features and is heavily based on BOOST and SDL. We can train you in some of the libraries used, but learning all of them would be a big hurdle.
* Experience with multiplayer games, in order to have a good idea of what multiplayer lobbies of other game look like, and (more importantly) a good idea of the social behaviours of multiple MP communities, how teams are formed in games and things like that.

==== Milestones and deliverables ====

* A first milestone would be a presentation summarizing the different studies, and the proposed interface. preliminary informal stages would probably be desirable, to make sure the proposed idea is already a consensus within devs
** Study of other MP game-matching interfaces and functionalities
** Study of other MP communities
** Study of other MP moderation practices
** Study of the Wesnoth MP community, including needs, various opinions from different developers and players
* A second milestone would be the main code delivery. Code should be functional for it will be delivered in the next Wesnoth development release

=== See also ===
[[SummerOfCodeIdeas|Summer of Code Ideas]] - The root where all information regarding SoC is (or better should be) linked from.

@@ Line 48: / Line 48: @@
 === See also ===
 * [[SummerOfCodeIdeas|Summer of Code Ideas]] - The root where all information regarding SoC is (or better should be) linked from.
-* [[http://www.wesnoth.org/wiki/EasyCoding#GUI2_related_features]] Easy coding tasks regarding the GUI.
+* [[EasyCoding#GUI2_related_features]] - Easy coding tasks regarding the GUI.
-* [[http://wesnoth.org/wiki/GUIToolkit]] Main entry point for the new GUI.
+* [[GUIToolkit]] - Main entry point for the new GUI.
 [[Category:Summer of Code]]

@@ Line 47: / Line 47: @@
 === See also ===
-[[SummerOfCodeIdeas|Summer of Code Ideas]] - The root where all information regarding SoC is (or better should be) linked from.
+* [[SummerOfCodeIdeas|Summer of Code Ideas]] - The root where all information regarding SoC is (or better should be) linked from.
-[[http://www.wesnoth.org/wiki/EasyCoding#GUI2_related_features]] Easy coding tasks regarding the GUI.
+* [[http://www.wesnoth.org/wiki/EasyCoding#GUI2_related_features]] Easy coding tasks regarding the GUI.
-[[http://wesnoth.org/wiki/GUIToolkit]] Main entry point for the new GUI.
+* [[http://wesnoth.org/wiki/GUIToolkit]] Main entry point for the new GUI.
 [[Category:Summer of Code]]

← Older revision		Revision as of 19:38, 15 February 2009
Line 30:		Line 30:

	Interaction with the Add-On server/forum should be explored.		Interaction with the Add-On server/forum should be explored.
		+
		+	An additional feature that could be considered is more secure random number generation to prevent cheating. At the moment, random numbers are generated on the client side. Things could be changed

	==== Required knowledge and talent ====		==== Required knowledge and talent ====

← Older revision		Revision as of 23:03, 18 March 2008
Line 47:		Line 47:
	=== See also ===		=== See also ===
	[[SummerOfCodeIdeas\|Summer of Code Ideas]] - The root where all information regarding SoC is (or better should be) linked from.		[[SummerOfCodeIdeas\|Summer of Code Ideas]] - The root where all information regarding SoC is (or better should be) linked from.
		+
		+	[[Category:Summer of Code]]

@@ Line 34: / Line 34: @@
 ==== Required knowledge and talent ====
-* A fair amount of experience with C++ is required. Wesnoth uses some advanced C++ features and is heavily based on BOOST and SDL. We can train you in some of the libraries used, but learning all of them would be a big hurdle.
+* A fair amount of experience with C++ is required. Wesnoth uses some advanced C++ features and is heavily based on BOOST and STL. We can train you in some of the libraries used, but learning all of them would be a big hurdle.
 * Experience with multiplayer games, in order to have a good idea of what multiplayer lobbies of other game look like, and (more importantly) a good idea of the social behaviours of multiple MP communities, how teams are formed in games and things like that.

@@ Line 10: / Line 10: @@
 Some ideas that we had (but that are in no way mandatory):
 * Having a simple room system? Again, inspired by IRC
 * Having some way to find the type of games you are interested in. filtering by: