Journals

After a few weeks of playing Quake Wars on and off I finally have my own stats page!! Rather unimpressive at the moment but i'm working on it:

http://stats.enemyterritory.com/profile/197600?page=summary

Sven Coop Campaign

It's time to kick ass and chew bubble gum , but I'm all outta good drivers .
Well , that's my story in a short line .
But the enthusiasm reappears in me , and I want to finish the Sven Coop Campaign . I have 2 maps done , and the third one started .
When I finish that too , all I have to do is learn again (2 months without mapping !! ) how to use the trigger_changelevel and info_landmark ..... and make the maps seamless or what ...

Here's a sample video of the beginning of the second map .

WATCH OUT , SPOILER !!!

Note : You even don't see an entrance in that room . That's what I was talking , I didn't made that seamless yet ...

http://www.youtube.com/watch?v=n81pwvOK2oA

[EDIT] You'll see a small blue laser beam . That's a path for the sven coop bots ( I have my f9 button binded to it , and I also use f9 for Fraps)

It's been almost four years since I first joined TWHL.

Times flies when you're having fun.

So I volunteered to rewrite a tutorial because the original didn't work, and the original author was listed as no longer a member.

I must be crazy!

Because of the constraints under which I am submitting the new tutorial - constraints which make editing a little difficult - I shall post it here first, to make sure it looks okay and nothing is spelled incorrectly!

On the count of three, paste:

Add Fog to your Mod

by darkphoenix_68

(The mod originally posted by Highlander formed the basis of my work, but as originally posted it contained several errors that prevented it from working. The TWHL Admins kindly agreed to allow me to revise his tutorial. Needless to say, without his original tutorial as a starting point, I would never have gotten this code to work as it now does. Additional credit (as originally extended by Highlander) goes to Confused, Sysop, and Cause of Death.)

[list][li]Requires Half-Life SDK 2.3, a little coding experience, and your favourite Mod compiler![/li]
[li]Assumes you know how to compile DLL files and create/revise a Mod.[/li][/list]

If you want to add fog to one or more maps in your mod, this tutorial will show you how to do it.

This fog is a visual effect, controlled by a point entity (an [ent]env_fog[/ent]) which you can insert into your level. It can be toggled on or off as required. It can be any colour you choose, and its apparent density is controlled by setting the start and end distances over which the effect is applied.

Sadly, the code also has its limitations:
[list]
[li]It only works under the OpenGL video driver; neither Software nor Direct3D are currently supported. (I did look briefly into adding Direct3D support, but since I don't actually use it - and since it never worked under the initial implementation either - I decided to leave it as an exercise for the reader! )[/li]
[li]Being point-based rather than brush-based, you would need some careful level design if you wanted both foggy and fog-free areas. Its switchability helps here -- for single-player levels, anyway! (I suspect brush-based fog could be developed by looking into the water-handling code; that's another exercise for another time!)[/li]
[li]The way the code handles [val]sky[/val] leaves a little to be desired, with the [ent]skybox[/ent] occasionally flickering into partial view through the fog as you turn. Again, careful level design could resolve this issue! Other than this flicker, the sky will be fully masked by your fog colour![/li]
[/list]

So, if you want to go ahead and add support for this client-based point-entity fog to your mod, read on.

General Comments

The following tutorial is quite code-intensive, and unfortunately the bbCode used here on TWHL does not preserve indentation, so it may look a little messy. However, it does work (I've tested it extensively) and it will work whether it is indented or not. Obviously, for your own sanity, you may wish to reindent as appropriate! The other artifact of the site itself of which you should be aware is that some lines of code wrap when they reach the edge of the page; it should be obvious, but watch out for it anyway!

I have scattered additional

[green]// explanatory comments[/green]

throughout the code. These form part of the tutorial, but are (obviously) not necessary to the compiler; however, I hope they will assist in explaining what is going on. (Or, I guess, make it quite clear that I do not know what is going on...)

Existing code (shown for reference and/or context) is in

[val][i]blue italics[/i][/val]

. In many cases I have given approximate line numbers; these are only approximate, because my files contain other code changes not relevant to this tutorial... If the line number does not help you locate the piece of code I am changing, your [ins]Find...[/ins] tool is your friend!

Files to be edited are shown in

[red][b]red[/b][/red]

.

Server-side: The ClientFog Class

First we need to create support for the [ent]env_fog[/ent] entity. This is done server-side (in the

dlls

directory, and the associated Project/Workspace.)

Open the

[red][b]dlls/effects.cpp[/b][/red]

file in your favourite editor and add the following code at the end of the file:

//=======================
// ClientFog
//=======================
extern int gmsgSetFog;

[green]// This is the flag defined by the env_fog entity[/green]
[/pre][pre]#define SF_FOG_STARTOFF		0x0001

LINK_ENTITY_TO_CLASS( env_fog, CClientFog );
[/pre][pre]
[green]/*
// While a CClientFog constructor is not actually necessary for
// this code, you might find use for one down the track,
// in which case it may look like this:
CClientFog *CClientFog::FogCreate( void )
{
	CClientFog *pFog = GetClassPtr( (CClientFog *)NULL );
	pFog->pev->classname = MAKE_STRING("env_fog");
	pFog->Spawn();
	return pFog;
}
/*[/green]
[/pre][pre]
[green]// Spawns our env_fog entity and sets the m_active flag.[/green]
void CClientFog :: Spawn ( void )
{
	pev->solid			= SOLID_NOT;
	pev->movetype		= MOVETYPE_NONE;
    pev->effects		= 0;
	if ( pev->spawnflags & SF_FOG_STARTOFF )
		m_active = 0;
	else
	{
		SetThink( FogThink );
		pev->nextthink = gpGlobals->time + 0.01;
		m_active = 1;
	}
}
[/pre][pre]
[green]// Reads salient values from the env_fog entity[/green]
void CClientFog :: KeyValue( KeyValueData *pkvd )
{
    if (FStrEq(pkvd->szKeyName, "startdist"))
    {
        m_iStartDist = atoi(pkvd->szValue);
        pkvd->fHandled = TRUE;
    }
    else if (FStrEq(pkvd->szKeyName, "enddist"))
    {
        m_iEndDist = atoi(pkvd->szValue);
        pkvd->fHandled = TRUE;
    }
    else
        CBaseEntity::KeyValue( pkvd );
}
[/pre][pre]
[green]// Essentially turns our fog effect on/off by sending a message to the client.
// Anything which changes m_active should force a FogThink.[/green]
void CClientFog :: FogThink ( void )
{
	if ( m_active )
	{
        MESSAGE_BEGIN( MSG_ALL, gmsgSetFog, NULL );
        WRITE_SHORT ( pev->rendercolor.x );
        WRITE_SHORT ( pev->rendercolor.y );
        WRITE_SHORT ( pev->rendercolor.z );
        WRITE_SHORT ( m_iStartDist );
        WRITE_SHORT ( m_iEndDist );
        MESSAGE_END();
    }
	else
	{
        MESSAGE_BEGIN( MSG_ALL, gmsgSetFog, NULL );
        WRITE_SHORT ( 0 );
        WRITE_SHORT ( 0 );
        WRITE_SHORT ( 0 );
        WRITE_SHORT ( 0 );
        WRITE_SHORT ( 0 );
        MESSAGE_END();
	}
}
[/pre][pre]
[green]// Called when the entity is triggered.[/green]
void CClientFog::Use( CBaseEntity *pActivator, CBaseEntity *pCaller, USE_TYPE useType, float value )
{
	if ( ShouldToggle( useType, m_active ) )
		m_active = !m_active;
	SetThink( FogThink );
	pev->nextthink = gpGlobals->time + 0.01;
}
[/pre][pre]
[green]// These macros set up the save/restore code for the CClientFog object[/green]
TYPEDESCRIPTION CClientFog::m_SaveData[] =
{
    DEFINE_FIELD( CClientFog, m_active, FIELD_BOOLEAN ),
    DEFINE_FIELD( CClientFog, m_iStartDist, FIELD_INTEGER ),
    DEFINE_FIELD( CClientFog, m_iEndDist,FIELD_INTEGER ),
};

IMPLEMENT_SAVERESTORE(CClientFog,CBaseEntity);

The declarations for the above code need to be added to

effects.h

(you'll note some of the classes defined in

effects.cpp

have their declarations in the .cpp file, but we need to make our fog visible to other files!) Place the following code at the bottom of the

[red][b]dlls/effects.h[/b][/red]

file, just above the final

[val][i]#endif[/i][/val]

line:

//=======================
// ClientFog
//=======================
class CClientFog : public CBaseEntity
{
    public:
[green]/*
// As stated above, this constructor is not needed; add if required!
        static CClientFog *FogCreate( void );
*/[/green]
        void Spawn( void );
        void KeyValue( KeyValueData *pkvd );
        void EXPORT FogThink( void );
        void Use( CBaseEntity *pActivator, CBaseEntity *pCaller, USE_TYPE useType, float value );
        int m_iStartDist;
        int m_iEndDist;
        bool m_active;
        virtual int Save( CSave &save );
        virtual int Restore( CRestore &restore );
        static TYPEDESCRIPTION m_SaveData[];
};

This gives us the code we need to initialise our fog to the values set in the [ent]env_fog[/ent] entity. However there are still a couple of minor problems to tackle...

Server-side: Fog Status Messages

Whenever a new player joins the server, it needs to send a fog status message to the client. There are three possible situations in which the client needs to be updated, and we need to cover them all:
[list]
[li]A new level is loaded;[/li]
[li]A new player joins a running multi-player server;[/li]
[li]A player respawns after dying.[/li]
[/list]

Our first problem is that we cannot directly detect a change of map. Let's change that by hooking into code which is called at every level change.

First we shall add our variable declaration to the bottom of

[red][b]dlls/globals.cpp[/b][/red]

:

DLL_GLOBAL int          gLevelLoaded;

Now we set it at the appropriate moment; let's edit

[red][b]dlls/world.cpp[/b][/red]

:

Somewhere around line #43, you will find:

[val][i]extern DLL_GLOBAL	int			gDisplayTitle;[/i][/val]

Add the following line below that:

extern DLL_GLOBAL	int			gLevelLoaded;

Now, down around line #479 you should find the

[val][i]CWorld :: Precache[/i][/val]

function, to which you need to add the following line:

[val][i]void CWorld :: Precache( void )
{
	g_pLastSpawn = NULL;[/i][/val]
	gLevelLoaded = TRUE;	[green]// Handles "level loaded" case[/green]

With that out of the way, let's handle the player spawning cases. First we'll declare our variable in

[red][b]dlls/player.h[/b][/red]

(somewhere around line #90):

[val][i]class CBasePlayer : public CBaseMonster
{
public:[/i][/val]
    BOOL                m_bRespawned; [green]// True when fog update msg needs to be sent[/green]

Now we can modify our player code to pull all of this together. Be brave; there are many small changes scattered through this next file. Open

[red][b]dlls/player.cpp[/b][/red]

-- and here we go!

First we need to find the following line (at around line #45):

[val][i]extern DLL_GLOBAL int		g_iSkillLevel, gDisplayTitle;[/i][/val]

and change it to look like this:

extern DLL_GLOBAL int		g_iSkillLevel, gDisplayTitle, gLevelLoaded;

A little further down you will find a whole list of

[val][i]int[/i][/val]

initialisation lines; look for:

[val][i]int gmsgTeamNames = 0;[/i][/val]

and add the following on the next line:

int gmsgSetFog = 0;

Just below that you will find

[val][i]LinkUserMessages[/i][/val]

function; add

gmsgSetFog

somewhere near the top, like so:

[val][i]void LinkUserMessages( void )
{
	// Already taken care of?
	if ( gmsgSelAmmo )
	{
		return;
	}[/i][/val]
	[green]// This basically registers "SetFog" as a known message to be sent to the server[/green]
	gmsgSetFog = REG_USER_MSG("SetFog", -1 );
[val][i]	gmsgSelAmmo = REG_USER_MSG("SelAmmo", sizeof(SelAmmo));[/i][/val]

Now you want to jump down to the

[val][i]CBasePlayer::PlayerDeathThink[/i][/val]

function; this will be somewhere around line #1150 to #1200. Right at the bottom of the function, just before the

[val][i]respawn[/i][/val]

call, you want to add the following:

[val][i]	//ALERT(at_console, "Respawn\n");[/i][/val]
    m_bRespawned = TRUE;	[green]// Handles "player respawned" case[/green]
[val][i]	respawn(pev, !(m_afPhysicsFlags & PFLAG_OBSERVER) );// don't copy a corpse if we're in deathcam.[/i][/val]

Down around line #2700 to #2800 is

[val][i]CBasePlayer::Spawn[/i][/val]

; add the following line right near the bottom of the function:

[val][i]	m_flNextChatTime = gpGlobals->time;[/i][/val]
	m_bRespawned = TRUE;	[green]// Handles "new player" case[/green]
[val][i]	g_pGameRules->PlayerSpawn( this );[/i][/val]

We're almost done. Now that we have detected all of the cases for which we need to send our fog status message, all we need to do is actually process that information. The best place to do that is in the

[val][i]CBasePlayer::UpdateClientData[/i][/val]

function, down around line #3800. You can probably insert the following snippet of code at any convenient point in this function; I slotted mine between the

[val][i]if ( m_iFOV != m_iClientFOV )[/i][/val]

and the

[val][i]if (gDisplayTitle)[/i][/val]

:

[val][i]
	if ( m_iFOV != m_iClientFOV )
	{
	:
	:
	}
[/i][/val]
    if ( m_bRespawned || gLevelLoaded )
    {
        CBaseEntity *pEntity = NULL;
        pEntity = UTIL_FindEntityByClassname( pEntity, "env_fog" );
        if ( pEntity )
        {
            CClientFog *pFog = (CClientFog *)pEntity;
			[green]// CClientFog::FogThink handles the actual message sending, so let's force a think[/green]
			pFog->pev->nextthink = gpGlobals->time + 0.01;
        }
		m_bRespawned = gLevelLoaded = FALSE;
    }
[val][i]
	// HACKHACK -- send the message to display the game title
	if (gDisplayTitle)
	{
	:
	:
	}
[/i][/val]

That's it for the server-side code. Before we leave the

dlls

directory, we can probably compile the server dll -- or leave it till we're fully finished; whatever works best for you!

Client-side: Incoming Messages

At this point, the server has initialised the fog, detected everything it needs to detect, and sent a fog status message hurtling through the void (sorry, bad pun!) towards the client(s). Now we just need to convince the client to catch them! To do that, we'll leave the safety of

dlls

and move over to the

cl_dlls

directory (and associated Project/Workspace!)

First we'll ask the HUD to catch the incoming message. Open

[red][b]cl_dlls/hud.cpp[/b][/red]

and look for

[val][i]__MsgFunc_GameMode[/i][/val]

at around line #130. Add the following:

[val][i]int __MsgFunc_GameMode(const char *pszName, int iSize, void *pbuf )
{
	return gHUD.MsgFunc_GameMode( pszName, iSize, pbuf );
}
[/i][/val]
int __MsgFunc_SetFog(const char *pszName, int iSize, void *pbuf )
{
    return gHUD.MsgFunc_SetFog( pszName, iSize, pbuf );
}

Further down, around line #300, you will find a whole list of

[val][i]HOOK_MESSAGE[/i][/val]

macros in no particular order. Add:

HOOK_MESSAGE( SetFog );

to the list. (I added it between

[val][i]HOOK_MESSAGE(TeamInfo);[/i][/val]

and

[val][i]HOOK_MESSAGE(Spectator);[/i][/val]

, but I don't suppose its placement is critical. It might almost be nice if the list was sorted alphabetically, but that's up to you -- and more to the point, it may break everything, so let's leave that for another time! )

To follow through on our changes to the

.cpp

file, open the

[red][b]cl_dlls/hud.h[/b][/red]

file; look for

[val][i]	int  _cdecl MsgFunc_Concuss( const char *pszName, int iSize, void *pbuf );[/i][/val]

somewhere near line #640, and after it add:

int  _cdecl MsgFunc_SetFog(const char *pszName, int iSize, void *pbuf );

Now that we've caught the message from the server, let's process it. To do this we need

[red][b]cl_dlls/hud_msg.cpp[/b][/red]

. Before we do anything else, let's declare the variables we're going to use. After the initial

[val][i]#include[/i][/val]

s and

[val][i]#define[/i][/val]

s, add the following:

float g_fFogColor[3];
float g_fStartDist;
float g_fEndDist;

A couple of lines down from there, we shall reset our fog distance values when we reset the HUD:

[val][i]int CHud :: MsgFunc_ResetHUD(const char *pszName, int iSize, void *pbuf )
{
	ASSERT( iSize == 0 );[/val][/i]
	g_fStartDist = 0.0;
g_fEndDist = 0.0;

Right at the bottom of the file, we'll add our

SetFog

function which actually interprets the received message:

int CHud :: MsgFunc_SetFog( const char *pszName, int iSize, void *pbuf )
{
    BEGIN_READ( pbuf, iSize );
    g_fFogColor[0] = (float)READ_SHORT(); // R
    g_fFogColor[1] = (float)READ_SHORT(); // G
    g_fFogColor[2] = (float)READ_SHORT(); // B
    g_fStartDist = (float)READ_SHORT();
    g_fEndDist = (float)READ_SHORT();
    return 1;
}

Where The Magic Happens

We're on the home straight now. We've done everything except actually display the fog. (Well, almost everything, but I'll get to that!) The file we want to edit now is

tri.cpp

. This is the file which confused me the most when I was originally trying the get the code to work -- but it was only once I started looking further afield that I solved the puzzle. Anyway, without further ado, let's open

[red][b]cl_dlls/tri.cpp[/b][/red]

. Just after the initial

[val][i]#include[/i][/val]

s and

[val][i]#define[/i][/val]

s, we'll access the variables we set up previously:

extern float g_fFogColor[3];
extern float g_fStartDist;
extern float g_fEndDist;

After the

[val][i]extern "C" { ... }[/i][/val]

declarations, we'll add the heart of the whole thing:

void RenderFog ( void )
{
	static float fColorBlack[3] = {0,0,0};
	if (g_fStartDist > 0.0 && g_fEndDist > 0.0)
		gEngfuncs.pTriAPI->Fog ( g_fFogColor, g_fStartDist, g_fEndDist, 1 );
	else
		gEngfuncs.pTriAPI->Fog ( fColorBlack, g_fStartDist, g_fEndDist, 0 );
}

And now for the thing that really confused me. At the bottom of the file we have

[val][i]HUD_DrawNormalTriangles[/i][/val]

and

[val][i]HUD_DrawTransparentTriangles[/i][/val]

. Extensive testing led me to the inescapable conclusion that each apparently does the other's job:

[val][i]HUD_DrawNormalTriangles[/i][/val]

handles "transparent" faces and

[val][i]HUD_DrawTransparentTriangles[/i][/val]

handles -- well, everything. Of course, all you really need to know is to change the latter function as follows:

[i][val]/*
=================
HUD_DrawTransparentTriangles
[/val]
[green]Despite the name, it appears that this actually controls
non-transparent entities and world brushes[/green][val]
=================
*/
void DLLEXPORT HUD_DrawTransparentTriangles( void )
{[/val][/i]
    RenderFog();
[val][i]#if defined( TEST_IT )
//	Draw_Triangles();
#endif
}[/i][/val]

That's it! Compile that, and if all goes according to plan you'll have working fog.

(Well, there's still that "almost" to take care of. I'll get there in a second. Just as an aside, though, while we're here: see that

[val][i]#if defined( TEST_IT ) ... #endif[/i][/val]

? While playing with this file I compiled in the

[val][i]Draw_Triangles()[/i][/val]

code. The whole thing (ie, Half-Life) fell over while trying to start a map, so I hastily got rid of it again. As soon as I'm done with this tutorial I shall probably clean all that code out to make the file a little neater...)

The Final Step

So what remains to be done? Adding the [ent]env_fog[/ent] entity to your map, of course. If you use Valve Hammer Editor, you can add the following to whichever FGD file you are mapping with:

@PointClass base(Targetname) size(-16 -16 -16, 16 16 16) = env_fog : "Client Fog"
[
    startdist(integer) : "Start Distance" : 1
    enddist(integer) : "End Distance" : 1500
    rendercolor(color255) : "Fog Color (R G B)" : "0 0 0"
	spawnflags(Flags) =
	[
		1 : "Start Off" 	: 0
	]
]

Since VHE does no sorting of its own, it probably makes sense to add this between [ent]env_explosion[/ent] and [ent]env_global[/ent] -- ie, alphabetically! You will now be able to add [ent]env_fog[/ent]s to your maps - although be warned, I'm not sure what will happen if you have more than one per level. I'd imagine if you had several with different colours, you could trigger them off and on to change the colour of your fog - but I have not tested that!

Unfortunately I am not familiar with any other editors used to make HL maps. No doubt they have a way of adding new entities, similar to the FGD file in Hammer -- but you'll need to figure that out for yourself! Sorry...

Wrap Up

What I have done is produce a small (and exceedingly ugly) test map for you to check out. I guess you could play with that to add multiple [ent]env_fog[/ent] entities, or whatever else you wanted to try. In the map you will find several transparent objects ("texture"-rendered and "solid"-rendered) because that was what I was having the most difficulty with initially. You will also find a large target which, if shot, will toggle the fog on and off.

It is quite a bit of coding to get to this point, but I hope my directions have been clear enough that we all arrived here with code which compiles and, y'know, actually works! If you have any problems let me know and I'll see if I can help out.

Have fun!

I have completed TheStockades. The map might still have some bugs tho... but i dont plan on adding anything new soon. Rate plz!
________
TheStockades v1.4 are here!
http://twhl.co.za/vault.php?map=5150

It has lots of new cool features, like 2 new Events, Modified bosses, and 2 new boss. it also has 9 new areas!

More info: The map now has smarter enemys, thanx to muzz and info_node, and it also has lots of bug fixes (altho it still has some in the new areas)

Here are some images: (note: from patch 1.2)

Me Near the currently final boss... or atleast whats left of himMe in a nice elevator-connected-to-a-duct near a bullchicken.Me fighting the final boss.Me in a cool room ^_^Me a bit away from a gonome thats chucking flesh at me Me fighting a boss :UMe near spazzed doggies!

Joined: 2nd May 2007 (500 days ago)

As I promised , I will post one more GIF . I'm not bored anymore , so you'll not see gifs from me for a long time .

Here's the gif . I think it shows up faster in ff than in windows's fax viewer .

A new competition lurks in the distance.

Writing the brief now, but it'll be a day or two ;o

Well, I've been hooked with the Unreal 3 Engine nowadays, we got licenses at school to use it, so that really puts on some pressure to learn it.

First off, they streamlined the layout of the editor and tools with 3dstudiomax and a little Maya, you can easily import new content and export maps. The placement and lightning of models and props is also really easy. And the interface is nice to work with.

But, there's one thing. And that is that it runs fine on the school computers, but the editor just doesn't seems to want to work on my own computer, which is rather annoying since I will need to do a large portion of the work at home, mainly because I only got 8 weeks to learn all the bits n bobbles of the engine, make a decent playing map that will be judged by others then the teacher. And make sure the rest of my team gets the idea, since they never have made maps for games before.

I suppose, that in reality it doesn't differ a lot from any real-life job situation with tight deadlines. Funny thing is, i actually enjoy this kind of pressure, it really allows people to push themselves to the edge and go beyond.

Oh, they also upgrade to max 2009, which seems to lack something called stability on the older school computers....

Welcome to the HEV Mach 4 Protective System, for use in hazardous environment conditions.

High Impact, Rickroll Armor; Activated.
( add to it :3 )

Yeahey! 800th login...200 more to go
logs in and out of TWHL repeatedly
LOL

On very rare occasions, you find something so perfect on the internet that you can sit there, staring at it for hours, and wonder how the fuck something filled with so much fail (see: youtube, 4chan, SA, etc) can produce something so awesome.

I experienced this yesterday, researching something for my new programming project. This article on parsing .MAP files and creating faces suitable for 3D display is the most awesome thing I have seen all year.

I have no idea how much time this has saved me, but I put it in the ballpark of: fucking ages. I've mirrored it on my kkore space for presevation; the original host is dead, and I was lucky to find it with google.

Shit, how long's Oxihosting been down? I didn't notice 'till right now. My profile is in ruins.

Copied from Blog

Male Gamers Playing as Female Game CharactersI've been meaning to write about this for a while because while playing a mod called 'Killing Floor' for Unreal Tournament 2004 I decided to play as a female character for a change. Among all the other players I was the only female character.

I joined the only server that came up because the mod had obviously lost interest and half way through amongst all the French someone asked me why I was playing as a female character and then rudely remarked "it was kinda gay".

First of all what led this person to assume I was a guy playing as a female and second of all what makes it gay? I mean I am a male, yes but I guess he hasn't seen many females play games.

I didn't really say much to him because I just thought what a stupid thing to say. So I just asked what makes it gay and he never replied...

But this goes back to my topic...Is it wrong to play as a female character?

It started a while back when I installed Elder Scrolls Oblivion for the thirteenth time and decided for a change to play as a female. It certainly made the game different because of the fact the NPC's addressed me as ma'm or miss and the new sounds when I attacked were refreshing. Although my mother came in and watched me play for a while so I explained to her what it was about etc and when I switched to third person I recall her saying..."You're a girl? That's kinda weird." (Thanks mum)

So ever since I've been playing as female character because it's refreshing and because there aren't enough of them in games.

This is partly why I am looking forward to Mirror's Edge which follows the role of Faith, a female character.

I suppose this topic is kind of steering towards Feminism which is a topic I'm not too knowledgeable about. I even have a friend who has a female avatar in Guild Wars and I remember saying it was kind of weird (this was before I tried playing as a female character)...So perhaps before people say it's weird, they should try it themselves.

But yeah, is it geeky for a male player to select a female avatar or do you think it's perfectly fine? I'm interested in what you have to say if you're reading this.

*While surfing for a picture to post at the top I found this interesting topic which is similar to mine:

http://news.filefront.com/chinese-mmo-bans-males-from-playing-female-characters/

Do give it a read.

I thought I'd add that just now I completed the Shivering Isles expansion for Oblivion using my female character and I realised how playing as a female helped me make decisions. For example I was pleased to see they added choices to the game and there is a point where you are forced to kill either the duke or the duchess. Playing as the female I chose to kill the duchess and take her role. Therefore if given the choice to be male or female, it does alter the experience from what I've seen. I could even replay it and see the different bits I missed not playing as a male for example... (Yes I did install it the same day I completed it...It's short! only took like 5-6+ hours I think...)

(Content used: http://www.sexysprite.com/images/UUWOVAIBBMHK.jpg - 05 September 2008)

Kut met peren.
One of my twin Corsair 1GB DDR SDRAM modules just died on me.

Immediately ordered a replacement, and wow, memory is freaking cheap these days. Thank you, Vista.