Some quick questions
Posted: Sun May 24, 2009 9:23 pm
Hello
I'm a newcomer to Oolite but an old hand with Elite. Back in the 1980s I had Elite on my Acorn Electron and subsequently on my Amiga 500. Many is the long hour I spent playing them. I tried Frontier and FFE but found them both disappointing due to the obsession with newtonian physics instead of gameplay. I've also tried out Eve Online but the combat system there is unsatisfying.
I've been playing around with Oolite and I have an immediate question. I'm using the latest 1.72 test version and I got a bit greedy (cough) and downloaded all the OXPs and installed them. The problem now is that my Jameson, fresh out of Lave, is getting his bottom kicked by a bunch of Mamba pirates who jump me once I come out of witchspace in Zaonce. My police rating is clean and all I'm carrying is some food bought with my first 100 credits. As Zaonce is a corporate state and should be relatively safe I'm assuming I'm being jumped by about 5 Mambas because of an OXP. I need to remove this OXP temporarily until I can get something a bit better than a pulse laser but I can't ascertain which OXP is doing this. Ideas?
On a connected subject, I spent about 3 years from 2003 onwards writing an Elite-a-like game using the Darkbasic Pro game language. I therefore have a pretty solid grasp of 3d maths and the sort of game design that a game like Elite uses. I'm wondering if I can contribute in a meaningful way to the coders who are improving Oolite. I know some C but I've got no experience of Objective C so I'd need to get my head into this area and find a decent IDE (presumably Visual C won't work with Objective C?). I'll download the source and take a look at that but my immediate question is to ask whether there are any docs summarising the architecture/design of the game, i.e. how the different .m files interrelate, what the coding convention is for the variables/arrays, etc.? When looking at someone else's code, particularly any code that does not have a lot of remarks, I find it easier to read docs first before diving into the code.
Cheers
Philip
I'm a newcomer to Oolite but an old hand with Elite. Back in the 1980s I had Elite on my Acorn Electron and subsequently on my Amiga 500. Many is the long hour I spent playing them. I tried Frontier and FFE but found them both disappointing due to the obsession with newtonian physics instead of gameplay. I've also tried out Eve Online but the combat system there is unsatisfying.
I've been playing around with Oolite and I have an immediate question. I'm using the latest 1.72 test version and I got a bit greedy (cough) and downloaded all the OXPs and installed them. The problem now is that my Jameson, fresh out of Lave, is getting his bottom kicked by a bunch of Mamba pirates who jump me once I come out of witchspace in Zaonce. My police rating is clean and all I'm carrying is some food bought with my first 100 credits. As Zaonce is a corporate state and should be relatively safe I'm assuming I'm being jumped by about 5 Mambas because of an OXP. I need to remove this OXP temporarily until I can get something a bit better than a pulse laser but I can't ascertain which OXP is doing this. Ideas?
On a connected subject, I spent about 3 years from 2003 onwards writing an Elite-a-like game using the Darkbasic Pro game language. I therefore have a pretty solid grasp of 3d maths and the sort of game design that a game like Elite uses. I'm wondering if I can contribute in a meaningful way to the coders who are improving Oolite. I know some C but I've got no experience of Objective C so I'd need to get my head into this area and find a decent IDE (presumably Visual C won't work with Objective C?). I'll download the source and take a look at that but my immediate question is to ask whether there are any docs summarising the architecture/design of the game, i.e. how the different .m files interrelate, what the coding convention is for the variables/arrays, etc.? When looking at someone else's code, particularly any code that does not have a lot of remarks, I find it easier to read docs first before diving into the code.
Cheers
Philip