Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Role Playing (Games)

Submission + - The Elder Scrolls' open source heritage

qubodup writes: "Two active TES-inspired free software game projects have drawn attention to themselves lately. OpenMW is a re-implementation of the TES3: Morrowind game engine, written in the D programming language, licensed under GPL3. In an interview the project's developer talks about how the project started, why he chose Git and graphics engine development.
DungeonHack (DH) is a FPRPG that is mostly inspired by TES2: Daggerfall's content generation system. In a recent review, the progress is illustrated in screenshots and videos and the short-term plans for the next release get introduced. Note: both engines use the infamous OGRE graphical engine."

Comment Re:Wild Goose Chase... (Score 1) 452

You are probably going to be quite disappointed by the explanation, but since you are "very curious" and this has clearly been keeping you up at night for the past week, I will indulge your curiousity by explaning this absolute knee-slapper of a joke..

First, the evidence:

> Says the guy working on a a rougelike RPG and who enjoys home spectrometry

Damn you, man! I just trawled through that guy's user page looking for (and unable to find) this alleged roguelike...

Then again, you DID say that it was actually a "rougelike." Does that mean it's like C&C: Red Alert?

See how the original guy misspelled 'roguelike'? He wrote "rougelike" and 'rouge' happens to be the French word for 'red'. The reply goes on to poke fun at this mistake. Though it could have been better. Particularly if he had consistently spelled 'rougelike'. Why else mention C&C: Red Alert as well?

Further evidence for this whole post being intended as a joke can be found on the user page itself, which you so kindly linked. Given the brevity of this page, one would have to be mostly blind to miss the link to the rogue-like. Especially when one has "trawled" the page, not "gave it a passing glance without bothering to look for a combination of letters which somewhat resembled the word that I was after".

So, you see, this is how we, the inhabitants of Slashdot, go about nitpicking eachothers posts. Indeed, a time honored tradition. Your turn!

Comment Re:I'm sorry, but you are wrong. (Score 1) 964

I am going to assume that you were either born in the US or came here at an early age (or another English speaking country, since you have not specified). Thus it should be safe to assume that you speak completely unaccented English, i.e.: you would get no different treatment over the phone. If someone cannot recognize that, then that person is most likely stupid. And like a lot of other people have been saying, that is not your problem, but theirs. Indeed, if stupid people were your problem, you would have a lot of problems.

Comment Re:I'm sorry, but you are wrong. (Score 1) 964

Dialect *is* highly based around social status (and thus, income). However, more importantly one usually chooses to speak with a particular dialect depending on the situation and how the speaker wishes to identify himself.

So, in your example many middle class 'white boys' wish to identify with the culture of their inner city heroes, but would not speak that way in a more formal setting. While even the most uneducated inner city black person could speak 'standard English' (exposure is impossible to avoid due to media), but chooses not to in order to show solidarity with his social group.

Comment Re:Wiki Wiki Wiki (Score 1) 528

I am curious to know why you moved away from Trac.

At my company we have been quite comfortably using Trac for both IT management and software development for over a year now. Clearly, it is best suited for the latter, but we have found it not to be lacking for documenting IT stuff.

For example, one thing that I find odd about what you are doing is putting problem descriptions inside the wiki page for each machine. Whereas (IMHO) Trac has this covered by its ticketing system where each issue has its own space for comments and followups. It is fully searchable, has various classifications (though we only use priority), and can be tagged with particular problem categories, or perhaps more importantly the names of machines involved.

I also find Trac's timeline invaluable for seeing what has been going on during the day or last couple of days, making sure new tickets don't get ignored, etc.. We also have an e-mail system setup where the non-IT masses (mostly chem E's) can report problems and have a ticket created from individual e-mails. SVN integration is handy as we keep all our various scripts in a repo. Everything is quite handily linked together by simply syntax like #31, r31, SomeWikiPage (for a ticket, revision, and wiki page respectively).

So, what made you change? Or were you only using the wiki feature of Trac and found it inadequate?

Slashdot Top Deals

Make sure your code does nothing gracefully.

Working...