Browsing the archives for the source tag.

Second map release: ep2_testcave2

Games, Projects

Second version of my map is now released! Its whole new cave to discover.

While creating this map. I learned lots of things. Example, in this map I started to use Source engines Entity Input Output system to create scripted doors and traps. I also learned howto create doors.

As this is my second map, it may not be as great as it could be. But I would really like to get some feedback from this level. If you can/want, I would like if you would record demo from playing this level trough, and then sending it to me so I can see how the level works.

There is some things I could improve. There isn’t lots of props and some of the materials can look awkward. I also don’t have any assault/nodegraph system build, so most of enemies just wait that you come and kill them.

In case somebody wants to see what I have done, but can’t/doesn’t want to download the map, here is a video from the map. Please note that it is major spoiler.

Download links are at my project page. Please let me know what you think about this map.

http://www.pelikoira.net/projects.
No Comments

Stats

Applications, Coding, Games, Internet

I don’t know why, but I love also all kind of stats. It’s just fun to have dozens of data and then analyze it with graphs and pie charts. Here is list of services that gives stats from various sources. I use all of them regularly.

  • Google analytics – Nice stats of the website
  • WoopraAwesome realtime website stats tracking
  • Feedburner – Nice feed subscribers/reach tracking
  • Webalizer – Bandwith monitor provided by my webhost
  • Hlstatsx – Most of my games are source games, so the Hlstatsx generates nice stats. (Open source version)
  • Etqw stats site – The official stats site
  • My own script that generates graphs from official ET:QW tracker
  • Steamcommunity – Steamcommunity gives gametime stats and also very detailed stats for some games (tf2,l4d)
  • Tweetstats – Very clean and nice stats for twitter usage
  • Twitter grader – Another cool stats tool for twitter
  • Twittercounter – Get graphs from followers
  • Cloc/ohcount – Some stats from my programming
  • Ohloh – Stats for almost every open source project. Code analysis.
  • mon.itor.us – Just pinging my site and checking that it’s up and running
  • Pisg – Stats from IRC
  • Last fm – All of the music I listen is listed on last.fm Also see my history/progress graph generated from last.fm stats
  • Wakoopa – Wakoopa tracks what apps I use and how much.
No Comments

Ohcount and Count Lines of code

Coding

Ohcount and Count Lines of Code (CLOC) counts size of code project. Mostly these aren’t very useful applications, but it is fun to see that I have written 300 lines of code in couple of days.

Ohcount is used Ohloh to generate source code reports. I was disappointed to found that i can’t use Ohcount to scan whole history of my repository, it only scans current status of code.

CLOC is written in Perl and Ohcount in Ruby. It maybe little annoying to compile Ohcount from source, but it is much faster than CLOC. If you want something that is easy to install, take CLOC. But if you are going to analysis more often than once, try Ohcount.

Here is example output from CLOC:


96 text files.
83 unique files.
33 files ignored.
http://cloc.sourceforge.net v 1.08 T=7.0 s (8.9 files/s, 547.4 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code scale 3rd gen. equiv
-------------------------------------------------------------------------------
PHP      49    588   172     1950 x 3.50    = 6825.00
SQL      1     58    87      277  x 2.29     = 634.33
BASH     10    54    133     261  x 3.81     = 994.41
CSS      1     46    5       192  x 1.00     = 192.00
Python   1     2     1       6    x 4.20       = 25.20
-------------------------------------------------------------------------------
SUM: 62 748 398 2686 x 3.23 = 8670.94
-------------------------------------------------------------------------------

And here is Ohcounts output from same file:

Examining 555 file(s)......

Ohloh Line Count Summary

Language Files Code Comment Comment % Blank Total
---------------- ----- --------- --------- --------- --------- ---------
php      58    2146 219     9.3%      716  3081
sql      1     277  87      23.9%     58   422
html     60    242  1       0.4%      38   281
css      1     192  5       2.5%      46   243
python   1     6    1       14.3%     2    9
---------------- ----- --------- --------- --------- --------- ---------
Total 121      2863 313     9.9%      860  4036

- Gestalts -------------------------------------------------------------------
Platforms: PHP, SQL, Scripting

Yep. There is some difference on results. I don’t know which one is more accurate.

I haven’t posted for a while because I have coded my main project. It isn’t public, but I will blog about it when it is ready. :) I try to blog more often.

No Comments

Git, simple source control system

Applications, Linux, Tutorial

If you project is bigger than 20 lines or it has over 1 user, you need source controlling system. If you are doing something very complex or you have many users it’s good to choose services like Google code or Beanstalk. (or something else)

But if you only need a source control system for your self, it’s not so clever to take remote source reporisity, because you can have your own source control system on your local machine!

Setting up svn server is much more difficult than setting up local git repository. I recommend to use git for every small local projects, because it is extremely easy to set up and it doesn’t require server to run.

So, install git (apt-get install git git-core) and then go to your projects directory and type:
Git init
Git add .

First command initializes git repository on .git folder and second command adds every file to new repository. In future when you add more files to project, just use “git add “.

Then do the first commit to get it working.

Git commit -a

Commit command opens default editor on your system. If you want to change it to another editor, add next line to your .bashrc file. (and reload bash to get it working :) )

export EDITOR=vim

Then just continue coding your project. When you want to commit more, just use previous command to do it. After you have done couple of commits you may want to see what you have done. Use “git log” to view latest commits.

When you type just “git” you will get list of sample commands that you will need later. More documentations can be found from gits website.

I recommend to try graphical git application: giggle. It makes it easier to understand branches.

Happy coding :)

No Comments