Missions Depot > OFP - Reviewed Missions
(Review Completed) <SP/COOP> OPERATION SPARK v1.5
haroon1992:
Version 1.5 available!
Release Date : 10/5/2011
Fixed several errors that appeared in v1.4 . Tested in SP and MP several times and result is perfect.
Check out the readMe to dig out scripts you like or want to use in your mission.
Scroll down for Download Link.
OPERATION SPARK
Type : Single Player/ Coop (3 players)
Game: OFP Resistance
Game Version Required : 1.96
Addons Required : JAM3, EditorUpdate103
JAM3
Editor Update 103
------------------------
Mission Description
------------------------
Soviets have invaded Kolgujev and are now slowly setting up defenses along the west coast. KDF(Kolgujev Defense Forces) have been no match for them. US is too busy in Afghanistan to respond KDF's call for help.
This is where British came, S.A.S operators are sent to the island to disable Soviets' AA capabilities.
Doing so will allow friendly forces to land forces to gain a foothold that'll stand against all forms of counter-attack. (Of course, not including nuclear strike :D)
------------------------
FEATURES
------------------------
Major :
- JAM3 High-Dispersion Weapon System
- Can be played in CO-OP (3-players)
- Non-basic Intro.
- Stealth-based mission.
- Advanced Detection System.
- AI Chase script.
- Nearly all enemy patrol routes are randomized.
- Main objectives' positions are randomized.
- High Re-playability
- Volumetric fog (Optimized since v1.35)
- Random Weather
- Background Music
- Alternate extraction by boat.
Minor :
-Custom texts
-Several radio menu options. (like Toggle Random Weather)
------------------------
Known Issues
------------------------
- The helicopter sometimes rotate on the ground, due to the EngineOn script, and this is obvious if you are playing in 4X mode.
- Possible lag with volumetric fog on low-end machines. (There is an option in radio menu to turn VFog off ;) )
- AI friends can sometimes ruin the gameplay or even blow their cover if the player isn't good with commanding AI.(For this, you can just let them stay at the start position by pressing ('~','1','6' ) )
------------------------
Change Log
------------------------
v1.5 (Current Version)
--- Quote ---- Fixed : Missing World.cfg error.
- Fixed : AIChase not running properly
- Fixed : Detection script errors.
- Fixed : Music player is now really disabled.
- Improved : Ending part of Intro scene
- Improved : AIChase is now much better.
- Improved : Roc script.
- Changed : Credits text layout at mission end.
- Removed : Intro texts.
- Numerous fixes in main.sqf and init.sqs
- Removed : Bumping hint message error.
- Fixed : Crew were turned-out of their armor.
--- End quote ---
--- Quote ---v1.4
Fixes
- Fixed : Second objective not get failed when detected
- Fixed : Overlapped tent at forward camp
- Removed : Dumb sniper in that tent
- Fixed : Various MP issues
[ - Second Objective only failing on Server
- Many scripts were not appropriately scripted for MP.
- Many other minor fixes. ]
- Fixed : One of the shilka position was at an odd place.
Changes
- Changed : Player units no longer equip high dispersion weapons
- Disabled : Music Player
- Removed : All MachineGun Nests to prevent the odd lighting effect on all over the base and outside areas.
- Tweaked : Detection script now gives players more time to maneuver with the situation.
- Tweaked : Volumetric fog execution
New
- Added : Background Musics
- New Scripts :
[ - playMusic.sqs - play the same bg music on all machines in MP
- StayUndetectedFAILED.sqs - make 2nd obj fail on all machine
- FOG_Camp.sqs - Fog at the enemy base
- FOG_FuelStation.sqs - Fog at the fuel station
- FOG_lz.sqs - Fog at landing zone
- Hrn_GetNearObjsFromArray.sqf - returns objs in array near to a certain obj
Pls open a script to see more detail about it. ]
v1.35
- Changed : Volumetric fog script. It is now much more performance friendly.
(Script will not create fog clouds if player unit is not near.)
- New : All units are now using JAM HD weapons. (Requires JAM3)
- Fixed : There were several dummy musics in Music Player.
- Tweaked : Fog placement.
- Several minor fixes.
v1.31
- New : keepEngineOn.sqs script to keep the extract heli's engine on.
- Added : betatesters to Credits list
- Added : A new small enemy encampment at the fuel-station west of main base.
- Added : Info about the new camp in "Notes" section of Briefing
- Fixed : Black Out not extending to the sides on large screens
- Fixed : A few grammar errors in briefing.
- Tweaked : Lone Ural is now moved further from base so that players will have much less chance to spot it.
- Removed : All songs except the one for intro. (to further reduce file size)
v1.3
- Fixed : Players were never able to stay undetected.
(It was caused by a minute mistake in one of the scripts.)
- Fixed : Ghost's position was used instead of group leader for domove commands in AI chase script
- Fixed : Shilkas should no longer *thump* at a certain position now.
- Fixed : Extraction by heli sometimes doesn't work, due to sloppy scripting.
- New : main.sqs, rewritten combined version of extractCheck.sqs and winCheck.sqs to make things clear and more organized as well as to improve performance.
- New : A few more scripts, like "Extraction_heli.sqs"
- Changed : Several name changes has been done to scripts.
- New : Some musics were added.
- New : Music Player, each player can listen any song they wish on his machine.
- Added : Music to intro.
- Tweaked : Camera angles and black outs in Intro to suit the music.
--- End quote ---
This mission has been reviewed and is now available for download at the Missions Depot:
Missions Depot
Regards,
Haroon1992
savedbygrace:
Played version 0.9
Overview
Great image, looks like you put some thought into that one but I think it would represent the image more if you placed an in game image as the background and made the brush strokes thinner to allow some of that image to show through. BUT, though this is not the type of image that I would prefer to see in my mission list to describe the mission, some folks may like it and at least it has the mission details on the flip page. If your intention is to make this the overview for a campaign, I suppose it works perfectly then. I also liked OP_Spark1 better.
Text correction below...
--- Quote ---A group of highly trained specialists, lead by Capt.Ghost, is tasked to destroy the AA Vehicles in an enemy camp, which have been shooting down many of our aircraft.
--- End quote ---
By the way, AAV is an acronym used by the U.S. military to refer to an Amphibious Assault Vehicle not anti air.
Intro
none
Briefing
PLAN
--- Quote ---US Marines have been facing difficultly on receiving reinforcements via air. The Soviet Union has setup several Anti-Air assets(AA) at key locations. For this purpose, the U.S. are sending their best men to silently disable those AA units. Multiple Operations will begin in the coming weeks, "Operation Spark" is one of them. Capt. Ghost, Sgt. Ice Man and Corp. Stalker are tasked in this Operation.
--- End quote ---
NOTES
The way that this section is written, it shouldn't be in script as personal hand written letters but rather print since you have links and intelligence that's addressed to the whole group in briefing form.
Corrected text below...
--- Quote ---CURRENT SITUATION
You'll start here and be extracted by air at these coordinates. This will be confirmed by HQ on radio.
SPARKER TWO BACKGROUND
A squad consisting of highly trained Black Ops, with an avg. of 10 yrs of experience. The team has received noticeably high amount of medals for their outstanding performance during the Soviet invasion on Malden.
--- End quote ---
Objective1
--- Quote ---Find and destroy all the AA assets located inside the soviet camp, code-named Sparkling Center 52.
--- End quote ---
All of the tips you offer are things that most people who play the game already know. If you still want to include them, place them in the readme document.
You could provide a tip on the different types of radio options you offer the player in game and what each does, similar to the toggle tips you have now.
Mention the Day/Night option.
Mention the Make it easier option
Mention the AI chase option
Mention the fog option
Mention the random weather option
Mission
I noticed in your init that you have this code.
--- Code: ---"HDjeep" setMarkerPos [0,0]
--- End code ---
Instead of setting it in the lower left corner of the map, just make it an empty marker in the editor and then set its marker type when ready..
--- Code: ---"HDjeep" setMarkerType "DOT"
--- End code ---
The mission starts with so many hints that have so much text, that it breaks the mood. The warning that stops the clock belongs in the README or in the beta thread, not in the mission.
The title was great.
The hint informing the player of where the enemy camp was, is not needed. People can figure these things out on their own.
You then throw another hint up about the fog and weather. Not needed.
The sidechat from HQ
--- Quote ---RECEIVED AND UNDERSTOOD, PROCEED WITH YOUR OBJECTIVE, YOU WILL BE EXTRACTED BY A BLACK HAWK AT THESE COORDS, OUT
--- End quote ---
What coordinates? There is no need to mention it anyway since the player should know the evac plan from the briefing.
--- Quote ---We move in, find those goddamn AAVs, put some satchals on them, and blow them up from a safe distance.
--- End quote ---
Misspelled satchels here.
You should also use upper case letters to start each line.
No offense but the side chatter between the operators seems unprofessional; almost as if they have never worked together before.
At mission start, I hear an explosion. I had no idea what it was until I get to the evac and the chopper is destroyed and the pilot standing outside of it. I notice you have the Special set to FLY in sqm and the pilot is not in it. That's what caused the crash.
The hint that I have been detected ruins the mood.
The follow up hint that informs me to go toe to toe with the enemy if need be is also not needed and ruins the mood.
My first play through, I was cautious. I only picked off guys if the situation called for it. I was able to plant the first satchel and circle west around the city. I took out the MG nest with no consequence. I also took out another lone patrol man with no consequence(However, I did hide his body). I made my way to the other side and was somehow spotted though I did not see anyone or see how they could have seen me. I went ahead and began popping targets as I spotted them, planted the other satchel and circled north around the city again, avoiding the second bmp that arrived, and the other infantry group that had arrived and was now circling the base in safe mode. I get far enough away to allow me to blow both charges and immediately get hit with another unnecessary hint.
BTW, I spotted a chair about 20 meters in the air above the tent behind the southern shilka.
My second play through, I went in as true Black Operators do; kill anything that stands between my muzzle and the package. I planted the first charge and took out all foot mobiles quickly, using the rpg I grabbed off of an outer patrol, I took out the responding ural before they could unload. I grabbed another RPG and blew the first shilka while blasting the second with the tube. Grabbed 2 more rpg's and finished the BMP's off. The place was quiet and dark and I walked into the fog like Batman.
Overall
I honestly thought that with all the trouble you went through to script detection triggers, that it would be much more difficult. I was actually looking forward to the challenge.
You're killing me with all the hints. Keep the communication between author and player out of the mission area. That particular radio chatter between operators belongs in an Intro, in an helicopter ride or something. Not on the ground fifty meters from enemy patrols.
The jeep offer for a ride was also not needed as the evac was only a short run away. (How did they know about it in the briefing anyways?)
Nevertheless, there is still potential here and I can't wait to see you improve it. Fix the ending and you'll have a non bugged mission. Fix some of the other things and you'll improve it.
Hope I don't sound too harsh.
haroon1992:
Thanks for your reply SavedByGrave.
As always, you've done a great beta-testing to a mission again.
And no, it isn't too harsh for me.
Actually, those hints were intended for my brother. But I'll be removing them from now on.
Glad that you liked the Overview image.
Actually, I made it with Microsoft Paint (Windows 7).
(At first, I planned to put op_spark1.jpg, but it text (OPERATION) appeared somewhat blurry and low quality in the Overview. Maybe I should have used a 512x512 resolution.)
--- Code: ---No offense but the side chatter between the operators seems unprofessional; almost as if they have never worked together before.
--- End code ---
I think you are saying about the Radio chats at the mission start, right ?
As my native language is not English, and I have no idea how real operators communicate, I wrote it based on the conversations in military games including BIS games.
I think I have only two choices, remove them or ask someone to correct them.
And there is also another radio chat for the helicopter ride.
I think I should just fix things up before saying anymore.
--- Code: ---The warning that stops the clock belongs in the README or in the beta thread, not in the mission.
--- End code ---
To admit, I don't think I clearly understand what you really meant in the above line.
But I think you are saying that I should put the warning hint in the ReadMe.txt
I'm now working on the next version and another mission.
(I tried to edit my First Strike mission, and tried to add a CAS feature, but I found no way of doing that.)
I have my last question.
Have you experienced lag in this mission?
(Especially when you enter areas where VFog is activated?)
Regards,
Haroon1992
savedbygrace:
No sir, no lag at all. I never tested the mission with any features off since it seemed pretty easy to begin with.
--- Quote ---I think you are saying about the Radio chats at the mission start, right ?
--- End quote ---
Yes. I offered corrections but I feel it was the context that seemed most unfitting. They were suppose to be highly trained operators but they spoke as though they had seen very few OPS together as a team. Most of what was spoken are the type of things that are drilled into operators during training. Also, the way the team leader addresses his team was disconnected in that he refers to them as people rather than mates. He also warns them against going mad? Shouldn't highly trained SF teams be disciplined enough to know better than to compromise the package with unreasonable force and tactics?
My suggestion...
--- Quote ---Ghost groupChat "Listen up, here's the deal..."
Ghost groupChat "We move in, find those goddamn AAVs, put some satchals on them, and blow them up from a safe distance."
Ghost groupChat "It's that simple men, so keep low and stay frosty."
IceMan groupChat " (IceMan) - Sounds easy when you say it Ghost."
Stalker groupChat " (Stalker) - Yeah, easy will get you dead. "
Ghost groupChat "Well, we all saw the intelligence on this one. This base's gonna be heavily protected!"
Ghost groupChat "Just remember, maintain stealth unless our cover is blown."
--- End quote ---
--- Quote ---Actually, I made it with Microsoft Paint
--- End quote ---
I guess I got the crap version with vista because I can't get it to insert text without a white background.
--- Quote ---But I think you are saying that I should put the warning hint in the ReadMe.txt
--- End quote ---
Yes sir. Your advice to the player and/or beta testers should be in your beta thread or in your readme. If you must, place it in your briefing on a separate page listed as "Authors Tips".
--- Quote ---I tried to edit my First Strike mission
--- End quote ---
Don't give up on that one. It was a great play and only needed some minor tweaking to make it better. Don't worry about the CAS, the chaos of infantry battle from corner to corner is great fun.
haroon1992:
You sure have such a great skill in writing to encourage someone into doing something.
Your friendly texts gave me enough energy to push my-self further into serious mission editing.
Now I've successfully updated Operation Spark to version 0.95
Its at 0.95 just because it's still not confirmed as "ready to play".
Means the mission now works from start to end.
I was in a hurry yesterday that I forgot to copy your feed-back, but I've fixed things as far as I remember.
I've also played the mission from start to end several times. And it run quite fine the last time I played.
And it helped me alot to find out more and more hidden bugs.
(I think I'm gonna use that same technic in all my future missions)
V0.95 Highlights (Pls see changeLog instead if you want quick details)
--- Code: ---- Added intro.(Not so good, but not so bad too, IMV)
- Explanations about the "Radio Menu" is now available both on the Briefing and the readme.
- An alternate extraction has been added. (In case the helicopter crashes or the pilot dies)
- Waypoints are added to aid the player.(You'll get no frustration with them, esp there's no "you must reach the waypoint" type except for extraction.)
- Added a few more units to make the mission much (or maybe a little more) harder.
- ReadMe has been tweaked for a cleaner view and it now contains more information.
- New Overview picture.
- Starting position of player is now a little farther from enemy camp.
- Some annoying radio chats are removed.
- Some other small issues are fixed.(Such as the mysterious flying chair)
--- End code ---
Paint
The new overview image is also made purely with paint.(Win 7)
Just overlapped two texts over another to create somethin like a shadow.
Hope this one's much more fun.
Regards,
Haroon1992
Navigation
[0] Message Index
[#] Next page
Go to full version