 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
you mean lunaran's coriolis force? that was cancelled ages ago (i believe his computer exploded and he lost everything), and the only other q3sp mod i know of wasn't that great (although to be honest, i never tried it) which i don't remember the name of.
and Sidrial.
Although sidrail or rial was a POS. DC wasn't bad considering it was made in q3. Not that Q3 is bad, but its not made for SP. Not that Q3 is bad, but its not made for SP.
i think what you mean is that q3 didn't have any SP style AI built in (like pathfinding) and only worked in bot style AI which, i would assume, isn't suitable for a SP game. i only say this because a lot of great SP games were made with the q3 engine and it is a powerful engine. It was made by the same guys who made ZenoClash.
They ended up making fake AI markers from uncollectable ammo for DC so that monsters could move. ANd the NPC's I think were all stood on invisible trains. q3 didn't have any SP style AI built in (like pathfinding)
Actually i think q3 had much better pathfinding, since it had to support bots that knew how to navigate a level. Compare that to q1, where the monsters just sort of randomly hump walls when they don't have a clear line of sight to their goal. The AI for monsters that act more like monsters would probably have to be written, but i think building it on top of bot code should be possible -- basically make them bots that move slower, don't pick up items, are a bit more stupid, etc. I think the main missing engine feature in q3 was probably saving/loading your game. You could probably create an SP game design that didn't require save/load (other than basic stats that you can store in cvars.) This is all speculation though; since i haven't looked at the q3 source or gamecode at all. Many sp games use the q3 engine. The question is how suitable is the original q3 engine for modders who want to make an sp mod.
RTCW was a professional mod, same as Alice - access to source and support as well as full time paid team makes a big difference.
spirit made heatmaps of multiplayer deaths from hundreds of demos:
http://www.quakeworld.nu/forum/viewtopic.php?pid=50185#p50185 Things that would be interesting to add: 1. frequency that a player is at those locations 2. divide total deaths by frequency of player being there, to get lethality -- i.e. likelyhood that each time you pass that point, you will die. useless to me, but still, really cool to see. the thing about dying close to walls jumped out at me in the first image. i guess it's just instinctive to try to get as much range as you can from the other guy?
Picking two players who play(ed) one map a lot was one of my ideas too. But seeing how much work it would be I do not think I will do it.
metl's ideas sound quite interesting too (plus imagine a duel with motion trails plus death spots, that might look sexy) but you'd need to edit mvdparser I guess (maybe it would be possible with the template). That and getting pushed to walls by explosion splash and lighting gun.
Definitely without any actual use for me too, but looking so fancy! :) Who put the Squad in danger in my sparetime, while I was on my work being out of order?
I check this site daily.
Someone should make another bogus level so you guys can have something to comment about. this reminds me of that Seinfeld episode with gorge and the whole friend and girlfriend thing and worlds colliding
yaknow..stuff Anyone try it out (any version?) A lot of reviews I've seen say it's pretty decent, was thinking of giving it a spin to tinker around in it or something. Looks kind of fun, would be a good break from FPS levels all the time.
If I'm remembering the engine correctly, I was helping some folks on a Torque game way back in 2004. Guess how far it got?
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |