How many of you, developers, once though: I really liked to develop a game.
The answer is simple: Most of you.
But beginning a game requires a lot of work. It requires a good idea that must be worked until exhaustion in order to develop a good starting base. This is the begging of the Game design.
Game design is the most important part of making a game. Is the Design that will define the success of a game. The game can be programmed by the best programmer in the world. That doesn’t mean the game will have success.
So what is game Design? Is a process that defines all the concept, rules, way of work of a game.
So, in the beggining of this phase, a lot of things must be done. The original idea must be polished by all the elements of the team. All the ideas must be putted above the table and discussed. Another thing that also helps a lot is to study similar games. And similar games are not necessarily games of the same type. Means games of the same market:
Example: You want to create a game for the Web, so one of the things you must do is explore all the games you can find (wikipedia is a wonderful starting point) of the same market (Web games in general).
And why? Because the type of game is not what matters. What matters are the concepts.
A good example are the GameForge games. Correct me if i’m wrong but games like Bitefight and DarkPirates aren’t exactly the same? User interface apart , the engine looks exactly the same: a place to shop, things you can buy to upgrade you character(Bitefight)/Ship(DarkPirates), find enemies to attack,etc. These two games are a good examples of similar concepts with different background stories.
If a good study of the market is a essential to start the design of a game, a brainstorm also is.
Only imaging new ideas, discussing them in several different perspectives, sometimes with people outside of the game development area (friends, family) can make your game unique, or at least different enough to attract different kind people to play it.
For example, in the current version of Orion’s Belt, the concept that separates Orion’s Belt for the other web games in the market is the Board game. It’s the “thing” that separates Orion’s Belt from all the other Massive multi Player web games in the web.
Of Course, because all members of team the have grew and news ideas have appeared and, in the last 4 years, we managed to build a good community that is always getting new idea. So, in Orion’s Belt 2 we will have concepts that are new in MMPOG (Browser based) and will make the game even more attractive to new players.
So, the ideas that you need to retain of this post are:
UPDATE: there was a problem with my wordpress and comments were shut down. I already took care of the problem. you can now comment this post
Shuffle a collection… hum, i must iterate the collection, change the elements from place, bummer… Well, not really.
The only thing you need to do to shuffle a collection is……. a sort.
Explaining: In C#, a Collection like List<t> (where T is the template element) has a method named Sort. Well, this method can receive has a parameter an IComparer<t>, an object that compares 2 other objects of type T.
The object that implement IComparer
public class ElementShuffle : IComparer<element> {
#region Fields
Random rnd = new Random()
#region
#region IComparer<element> Members
public int Compare( Element x, Element y ) {
if( x.Equals(y)) {
return 0;
}
return rnd.Next(-1, 1);
}
#endregion
}
In the above class, Element is the type of object of the collection, and ElementShuffle the implementation of IComparer<T>.
When you want to shuffle you collection you just need to call the Sort method:
List<Element> elements = new List<Element>(); ... elements.Sort(new ElementShuffle());
So what you gain by doing this? A much cleaner code, and a very easy way to do a shuffle.
But not the most efficient. Although it’s a clean way to make, like Carlos Rodrigues said in his comment to this post, this way may not be the most efficient. The Fisher-Yates algorithm:
public static void Shuffle( Listelements ) { Random rng = new Random(); int n = elements.Count; while( n > 1 ) { int k = rng.Next(n); --n; int temp = elements[n]; elements[n] = elements[k]; elements[k] = temp; } }
Source: Fisher-Yates algorithm - Wikipedia
Is a lot faster. Here are the results:
Time Fisher-Yates algorithm: 220,3168 ms
Time Comparer: 2213,1824 ms
With this post i learned a lesson: Sometimes the most elegant way to resolve a problem, is not the most efficient. It’s always good to check if your algorithm is more or less efficient than a “not so elegant way”.
In the end of 2007, i worked for a big company that still used in their sites asp.net 1.1. In fact, in their main site, the entire middleware is made in C# 1.1 (their site was launch at the beginning of 2008).
For this reason, there must still exist several applications made in ASP.NET 1.1 that will need some maintenance and new developments.
The challenge here is to develop a control that can simulate master pages in asp.net 1.1 similar to the one that exists in asp.net 2.0+. You make the master page using a .ascx control and make a .aspx webform has you would make in asp.net 2.0, meaning:
<asp:placeholder id='placeholder' runat="server"/>
<ctrl:contentplaceholder master="Master.ascx" runat="server"> YOUR CONTENT </ctrl:contentplaceholder>
where contentplaceholder is the control described below and master the name of the file of your master page. Has you will see below in the code, you can also omit this field and configure it’s value in the app settings of the web.config:
The code control is simple has below:
public class ContentPlaceholder : Control {
private string masterPage;
public string MasterPage {
get {
if( masterPage == null ||
masterPage == string.Empty ) {
return "~/" +
ConfigurationSettings.AppSettings["MasterPage"];
}
return masterPage;
}
set { masterPage = value; }
}
private void ChangeControls( Control src, Control dst ) {
while( src.Controls.Count > 0 ){
Control c = src.Controls[0];
src.Controls.Remove( c );
dst.Controls.Add( c );
}
}
private void LoadMaster( Control master ) {
PlaceHolder contentPlaceholder = (PlaceHolder)
master.FindControl( "placeholder" );
ChangeControls( this, contentPlaceholder );
ChangeControls( master, this );
}
protected override void OnInit(EventArgs e) {
Control master = Page.LoadControl( MasterPage );
LoadMaster( master );
}
}
In Resume, in the OnInit event the controls of the web page are removed from the aspx page, the content of the master page is inserted in the aspx, and the content previously removed is inserted in the placeholder of the master page:
I hope this example helps someone that still work with the old framework 1.1. This can be handy in big projects where you have hundreds of aspx to change.
Today i discovered something interesting with div’s.
Imagine that you have the following code:
<div id='mainDiv'> <div style='float:left'>Div #1</div> <div style='float:right'>Div #2</div> </div>
And you wanted that the div named “mainDiv” to have a background color. Well in IE7 everything works fine with the xhtml code
above. But in FireFox the “mainDiv” there is an unusual behaviour.
Below is a image that ilustrates what you get in Firefox (on the left) and what you get using IE7 (on the right) with the xhtml code above:
Notice that the main div, in IE7, warps all content, but in Firefox the div remains with a minimum height.
Io solve the problem you could try (has i did) to put a height in the “mainDiv”. Although it worked (for the content that i
had inside the Div), you never know what the the height of the mainDiv is going to be.
The correct solution for the problem must be one that adapts the height the mainDiv to the maximum height of it’s content.
The solution is simple:
<div id='mainDiv'> <div style='float:left'>Div #1</div> <div style='float:right'>Div #2</div> <div style='clear:both'></div> </div>
Adding the empty div with the style property “clear” set to “both” makes the mainDiv’s height extend to the full height of
it’s childs, making the xhtml generic for all browsers.
(UPDATE)
Due to the several solutions in the comments i will comment there here one by one.
Alternate Solution 1: the clearFix : thank to Joao A.
The solution in in fact very elegant and we only need to add something to your style sheet. The solution objective is to add
the pseudo element :after into that
“mainDiv”:
#mainDiv:after {
content: ".";
line-height: 0;
height: 0;
visibility: hidden;
display: block;
clear: both;
}
The pseudo element objective is to add some content after the element “mainDiv”. So the soluction passes by adding the
content “.”, removing the height of the content, hide that content and finnally clear both side of the div. in fact we are
doing the same has the original soluction without adding the extra div to the markup.
Alternate Solution 2: adding the float:left style to the “mainDiv” element : thanks to Vítor Pires.
This solution is actually very simple:
The solution is simple:
<div id='mainDiv' style='float:left' > <div style='float:left'>Div #1</div> <div style='float:right'>Div #2</div> <div style='clear:both'></div> </div>
Alternate Solution 3: adding the overflow style to the “mainDiv” element : thanks to Jeff and href=’http://btm.anfo.pl/’ target=’_blank’>BTM.
very simple just like the previous one. Add the overflow style property with the value ‘hidden’ or ‘auto’.
The solution is simple:
<div id='mainDiv' style='overflow:hidden;' > <div style='float:left'>Div #1</div> <div style='float:right'>Div #2</div> <div style='clear:both'></div> </div>
The only difference bettween the usage of overflow:hidden and overflow:auto is just that if you have a fixed height in the mainDiv, with overflow:hidden, the content will the content that surpasses the size of the div will be hidden, but with overflow:auto a sroll will appear.
The Solution 2 and the solution 3 are actually very good (and simple) to use in specific situation. if you want the content of the mainDiv to appear below it, than use solution 3 (or 1). Otherside, if you want the content to appear side by side with the div, use the float property in the main element.
At the end of my second day of full time development of the new version of Orion’s Belt, there is only one thing that i can say: I’m happy
My part is the battle (here is a shot for you that don’t know what the hell i am talking about). In some few words, the battle is no more than a chess like board game, with 8 different units on each side. Each one of them has it’s own attack, defense, range, special abilities and bonus.
In this 3rd version we decided not to change anything in terms of gameplay. The great optimizations will be in the Battle Core and in the Design. Why you ask? Because we consider that we have a pretty mature game, with a very strategic gameplay that our few (but very addicted) players love.
In the engine and in the design are our flaws.
The Engine is not extensible enough and all the Orion’s Belt Core is going to change. So, this is a good chance to upgrade all the code (meaning rewrite 90% of what we made in the past). Rewriting the code means:
All of this using .NET 2.0 (the use of generics will boost the Battle Core performance).
The new design will also help a lot. We want to make the battle page one of the most cool pages of the new Orion’s Belt version (never forgetting that this page must be cool and usable at the same time). Must be something that the players see and say: WOOOOOOOO.
And who is the guy that going to make this happen? Marco Vale.
Visit his site: it’s worth the time spent
Finally the new site of the zi-yu portal has been launched. It’s name is WebGames and it is a portal of web based games.
I think this portal can become a good reference of web based games for all players in the web.
Pre made a very good job. Speaking of Pre: Happy Birthday my friend!
.. Orion’s Belt 2.0 started it’s development… ![]()
Some minutes ago, i used a wonderful new feature of ASP.NET 2.0+, the offline page.
We just need to create a file named app_offline.htm and put it in the root directory of our web application.
If the file exists, every request is redirected to that file. As simple as that ![]()
I added recently a new section to my blog (on the right) named projects with the list of all projects that i am currently working in.
The projects aren’t all mine. Pedro and Tiago are also part of them. And, in some of them, we have persons who insert all the content in the website (like Astroligia and 4Pilares).
Currently there are only 7 projects (because the other are under development):
Centro de Copias, Bird Zone, Astrologia and 4 Pilares are still under construction. A lot of content is being added at the moment. Soon they will be at 100%.
Sms will soon be upgraded with a new design and new features.
The 2nd Version of Orion’s Belt will begin it’s development in january 2008. If everything goes well, in july, all of you can test (if you want of course) a new and improved version. We promise not to disappoint!
The name is MooTools, a very cool Javascript Library with object oriented and Ajax support. It simplifies the way you write your scripts because it has a very simple syntax and a lot of features integrated (like effects, Drag and drops, scrolls, Tooltips, etc, etc).
To test the framework, I started yesterday an Star Rating control in ASP.NET. I Clearly needed 2 things
The first was easy. I made a little search and found 2 very simple that i recommend: Komodomedia and pmob.
For this example I used the second. Both are well done, so i just picked one of them.
The second: do some code using mootools (Also very easy like is expected of any javascript framework)).
First Step: The creation of the control
The first thing to do is to to create a control that renders the star rating. The method GetRating is something abstract because, according to your implementation (and context of usage) this information will come from a specific place.
Let's just suppose that the we are in a context of an blog and the rating goes to a database and get's the average rating of the current post.
NOTE: for test proposes the method can return the value '3' (just to see some stars).
After create this control, create and aspx and insert insert the control into an ASPX test page. Don't forget to add the css of the star rating to the aspx. This css is available at http://www.pmob.co.uk/temp/star-rating.htm ( or simply download the zip at the end of the page
).
then compile and run the project. You should see something like this:
Second Step: The javascript
Now that we have the control running, we need to add to each star and event onclick so we can handle the user rating. To do this, we will the following script:
The Ajax type has an event named "update". This is very useful because you can simply put the html element you want there (In the example above I inserted the element "ratingMessage') and the response of the request will simply be inserted into the element.
After this step you will not be able to see anything moving (yet!) because the page that handles the ajax request, Formatter.aspx, isn't created.
Third Step: Process the Ajax request
Finally the page responsible for receiving the ajax request, the Formatter.aspx (to make the example simple, I used an aspx page but you can also any type of file).
The page only receives the value of rating (to simplify the example) and returns a text indicating which rating we choose.
You can download this example here