Search options (Page 4 of 10)

Ah hehe no more fun with him.

Are you humiliating the fat boss?

I don't use any exes. I just copy the needed paks into the Coop installation. You don't need other than that. To uninstall you just remove the folder.

From the readme:

Return to Castle Wolfenstein: Coop

* Installation:

- Copy all your rtcw pk3 files (mp_*.pk3, sp_*.pk3 and pak0.pk3) inside the main folder of this archive.
- Above is important, don't mix this with your current rtcw installation. You have to play this game as a complete new game.
- Double click rtcwcoop.exe and the game will start.
- You can open the console by pressing shift-escape.
- The source code for this project can be found at: http://code.google.com/p/bzzwolfsp/

If this has nothing to do with Coop. Try returning the files from the trash bin. If not, you can try reg seeker or regcleaner. Also how about giving it a different folder?

You know there is a mapping tutorial now? That tell pretty much anything needed to know.

Oh ok right. 100 is just regular max in normal play. You are welcome, glad to be of assistance.

First of all welcome aboard! There are currently no arrangements, but you are free to suggest a time. Luckily now there are games to join almost all time during evenings. If not join a server and someone might join shortly after.

What exactly do you want? No it is not same, but close.

You can play alone with same skill and same enemies as SP. Story and maps are same. Cvars allow us to alter game experience by admin. One can select proper settings from easy to nightmare, and for 1-8 players.

Only main thing is that it is not possible to see cutscenes in Coop. Basicly the gameplay is like SP, with few small changes.

I noticed you have program files in D but looks for user folder in C. Is your windows in C?

No. Why do you insist on making everything hard? Hardcode, why on earth? Slots... Huh? Markers should affect game entitity limit that is 1024, see /entitylist. Never needed /where fyi.

/dumprandommarker zone 1

just like /dumpcoopspawnpoint. As an allied. Give exact origin and angle of your aiming direction. And a zone key. Automatically added to ents file (or new file). Should not need where or type anything!

I am ok with new file for random markers and configureable using. A cvar should be there to be able define % or disable it. Dont want the user edit any files unless it is a must.

Point of using default locations was to save 1/3 of the work. Do mind that only the Ai whose default location it is should use it. 1/3 chance it simply would not teleport. This is simply to cut on work, ofc it is more random if not used.

But maybe if dumping markers would be as fast as I demonstrated it would not matter. Binded to a key and nothing else needed to do, nothing to fix manually. One key for each zone. Just run around bashing buttons. I can do this if I get the tools I need. The amount of random markers could be just about anything then.

Maybe if you want to evolve the vector idea (to extra random) there could be a code that makes the ai walk 1 sec to a random direction from the marker, stop and facetargetangles with the last marker. Maybe this could be when the random is set to >80% by admin. But  truth is that most ais you meet are navigating on their own and that is very random. Because one shot and they have their own will. The Ais you see first are the only that really matter.

Hmm. Maybe it is not so bad idea. I have used accum random and then used teleport targetname. But if I did not need to do this it would save half of the dev time.

What if the new approach is: if not markers present ignore. Check for each ai separately targetname ainame_rs1 and ainame_rs2 and one random is empty (default point). Then teleport to the markers. Mapper would add markers with the tools I presented above.

So in word of example

Following ai_markers are added nazi1_rs1 and nazi2_rs2 in ents.

Random 1 nazi1 stays same
Random 2 nazi1 will teleport to nazi1_rs1
Random 3 nazi1 will teleport to nazi1_rs2

If we want to do random actions or such other things, we can just use the old way with accum random. Now all is needed to run ingame dumping markers to apply. Do not make other random than individually for each ai.

Also I can tell by experience that you will run out of space and time if you have more than 3 random.

Edit.

This would cut the need for firstspawn. But still each ai script would have to be checked that nothing gets ruined. If there is any actions this cannot be used. Also possibly ai_marker count limit might need to be raised. Maybe if I get the tools I want I can make a run.