Welcome to Steelbeasts.com

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Volcano

Members
  • Content count

    7,068
  • Joined

  • Last visited

Everything posted by Volcano

  1. 17 NOV scenario: Civil War Dera Ghazi Part2-4019 SPECIAL CONSIDERATIONS: Need three COs: Blue vs. Orange vs. Red. Draft? No (unless we cannot even out the sides with players). This is a new scenario, which might need some balancing. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules. Civil War Dera Ghazi Part2-4019.zip
  2. INTENT: We are trying something new this year and we put all the "battle tested" scenarios into a list, and then randomly shuffled that list to create a TGIF play list. We are going down that list in order, choosing the next scenario to play from it rather than picking on a whim. Rather than post the list here (because the list can/will change throughout the year), a post will be created here before each Friday mentioning the scenario that will be played. You can then download the scenario and decide if you want to CO (post here if you want to take it), otherwise whoever volunteers on Friday will be the CO. CO GUIDELINES: Basic guidelines as to who can volunteer as CO from week to week. The intent is solely to afford everyone the opportunity to CO: No one may volunteer to be a CO back-to-back TGIFs. That is, if Mr. X volunteers to CO this week, he cannot volunteer to CO next week, but he can volunteer the week after that (every other TGIF). EXCEPTION: if a scenario requires more than two COs (i.e. because it has more than two sides) then there is no restriction on volunteering back-to-back with the previous TGIF. If no one volunteers to be the CO, then anyone can CO at the time of the event. So, in the example above, Mr. X can CO again that next TGIF if no one volunteers during the week. TGIF HOUSE RULES: There will always be bugs in software and Steel Beasts is no exception. More-so, functionality that exists in the Pro version which has carried over into Pro PE often creates unforeseen situations which allow for abuse and unrealistic behavior. To counter this, there are "TGIF HOUSE RULES" which are basically a set of ethical rules to allow "fair and realistic play" to keep scenarios from bogging down into the morass of shame. The House Rules are as follows (and the list may grow over time): DO NOT adjust the number of rounds per tube when calling off-map artillery strikes, because they currently have unlimited ammunition so it creates ridiculous situations. (Using number of rounds per tube with on-map artillery is fine because they are delivered differently and have finite ammunition.) If you want a long off-map artillery strike, just keep repeating it. //no longer necessary, now all off-map artillery barrages are capped at a 2 minute max duration. DO NOT adjust the duration when calling off-map artillery strikes -- for the same reason as rule #1. Also, like rule #1, setting the duration for on-map artillery strikes is OK. If you want a long off-map artillery strike, just keep repeating it. //no longer necessary, now all off-map artillery barrages are capped at a 2 minute max duration. DO NOT use support vehicles (supply vehicles, bridge layers, maintenance vehicles) for reconnaissance. DO NOT intensely study the enemy's side in the scenario in the Mission Editor. You can open it and look at both sides, but do not touch anything or evaluate the reinforcement criteria, events, conditions, routes and waypoints. Looking at the enemy side to get an idea of what they have is acceptable, especially since you have to do this to figure out which side to CO anyway. DO NOT use helicopters with the intent of causing a distraction for the AI. Everyone knows when this is happening, like when empty transport helicopters repeatedly return to "buzz" (fly over) enemy units at top speed again and again. Flying in on troop insertions and back out again is acceptable, as is engaging targets from a battleposition. DO NOT hover helicopters at maximum ("Normal") height in battle positions, to use as an ATGM platform or to act as a recon satellite or an AI distraction. This is unrealistic at the moment since the Scenario Designer currently has no way to restrict/limit/cap flight height because he may want to represent certain types of conflicts where long range air defense and air superiority fighters exist. At such time, if ever, that the Scenario Designer can specify a maximum flight height, then we can remove this house rule. NOTE: Failure to abide by the house rules will result in drastic measures by the TGIF coordinators, such as not posting the scenarios in advance, removing features from scenarios (like artillery and aircraft), or in the case of repeated violations, banning certain users from CO'ing, or from participating in TGIF. Also, the CO should strive to have all users on his side play within the guidelines of the house rules - since bad behavior of the side reflects badly on the CO. DISCUSSION: *AFTER* the scenario is played, feel free to post constructive criticism about the scenario here, so that it can be improved. All constructive criticism will be taken into account, but pissing and moaning will be ignored. Constructive criticism = complaints with specific suggestions Pissing and moaning = complaints with no specific suggestions DISCLAIMER: Keep in mind that: The scenario may change at the last minute depending on TGIF turnout. Any plan file that you may create may be rendered invalid by last minute adjustments to the scenario (if you are going to CO, it is better to save a plan AND take a screen shot of the plan as backup). Sometimes the TGIF scenario listing may not get updated due to real world situations. This TGIF scenario listing will continue until we point in time that it is deemed "too much trouble", which is the moment in which we determine that no one new is CO'ing, or the situation is no different than before, or that the matches are becoming unfair (due to both sides studying the enemy situation in advance). If this TGIF scenario listing turns into a mud flinging contest, because someone was sour about losing or in order to insult a scenario designer then posting the scenario early will end. The scenarios that appear in this listing are either new, classics, or at least played frequently and deemed "balanced". If you have a scenario that you think should be added to the play list then PM or create a post here about it.
  3. 10 NOV scenario: Island Invasion 02-4019-OMU SPECIAL CONSIDERATIONS: Draft? Yes. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules.
  4. Yes, that it intentional (I made the template). IIRC, its supposed to represent the AT-7 Saxhorn, which has about the same range (1km) and terrible penetration power as the Dragon. So, that is as close as we have.
  5. Thanks for the offer. Glad we had alternatives.
  6. Actually, we may have trouble having a host this TGIF. I guess we won't know until game time though...
  7. 3 NOV scenario: Deliberate Defense 03-4019-OMU-MAD SPECIAL CONSIDERATIONS: Draft? Yes. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules.
  8. Thanks, we will look into the smoke grenades not firing in manual mode on the M1.
  9. Actually, the main concession was that we only have one manual fire key (SHIFT+SPACE), so we have to use it as context sensitive. On the real M1 you can fire either coax or maingun manually, separately, but in SB we have it based on what weapon system is selected since we only have the one key to use. The design decision being: 'it's good enough'.
  10. We are aware of that, thanks. Actually, we will look back into this one - there seems to have been some confusion in the tracking of this bug. That said, we have been aware of it since SB1 but it has never been a priority (maybe we can change that now).
  11. OK, no problem, I will stick around for a while after TGIF to help.
  12. Your question is complicated to answer via forum post, I can help discuss it with you after TGIF if you remind me. The problem is that the Apply If and the region scoring method are two different things, and I would have to have you explain how you have the latter setup before I can help give you an intelligent/helpful answer. But basically... 1. Apply If is really used best when you want to great two or more sets of scoring possibilities. Like, if Blue did not do something, then you grade them by a separate set of standards. If Blue destroys the other side entirely, then you want to give them a full 1000 points for example, then the Apply If on the 1000 points score would reference the event that triggered when the other side was destroyed (usually the same even that ended the scenario), while the other scoring items for objects would not apply, because, for example, they Apply If only when Blue does not totally destroy the other side. If you don't separate the scoring like this with Apply Ifs, then you will end up with some strange scaled score possibilities. (In your example though, the region score (3:1) and Apply If would both happen, separately. The region score would always happen, 3:1 determination, then the Apply If would simply decide whether or not to award those points in the first place). 2. That said, you can have scoring work where you just give points away, then have an Apply If that determines when those points are given away. But this is probably not a good way to do it, since using events and conditions would work better. 3. If you are trying to do what I did in that scenario two TGIFs ago where a soldier counts as 1, while an AFV also counts as 1, then you would do this via a condition. Both sides have the same condition, one for each region (objective) and it compares who has the most "forces" between friendly and enemy. Lots of different scoring methods exist though...
  13. 27 OCT scenario: FEBA Madness (M1A1 v Leo2A4) v. 0.71 SPECIAL CONSIDERATIONS: Draft? Yes. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules.
  14. OK, I will look into that. I did already add the Ambulance to both, and will likely add repair, but maybe not supply (the supply trucks on blue are intended for the strong point defenders).
  15. 20 OCT scenario: Relief to Defense 01-multiparty-4019-OMU SPECIAL CONSIDERATIONS: FOUR COs are needed. Blue (US), Gray (DE), Green (UK) vs. Red (OPFOR). Draft? No. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules.
  16. OK, I looked. Regarding 6394 3761, this is an area of the theme called "mountain" and "rocky". Drag and traction are such that wheeled vehicles will not be allowed, and track vehicle movement could be restricted when going up steep inclines. That said, drag and traction aren't set in such a way that it would prevent all movement, but it seems to be deliberately set to make it restrictive in mountainous areas. So, I am reluctant to change it. I know that area looks relatively flat and not so mountainous, but for whatever reason, that partcular area is painted as base of the "Verkhiniy North Range". That said, maybe I can make the terrain look a bit more rough to give it away that it is not hospitable (more visual rock clutter, for example). EDIT: I fixed that now. Visually there should be no mistaking that the terrain is impassible (or at least very slow going). I think the problem was that it was "rocky" but had very little rock clutter visible, and looked like dirt. Actually, FWIW, after further investigation - I wasn't happy with some aspects of the appearance of the map theme so I edited some things quite a bit for "next time". It will behave mostly the same, but should look a bit different, at least.
  17. Regarding 6394, 3761, I will take a look at the terrain type in the theme. IT doesn't visually appear like soft sand, so it is possible that drag/traction is messed up. OK, I won't do anything about the rocks (I don't want to thin them out because the terrain is supposed to be rough); the user is expected to avoid the densely rocky areas. Of course unless thorough terrain recon is done in Planning Phase then the user won't know there are rocks in a particular area until the unit arrives at the rocks and gets stuck. To me that is part of the "fun" of discovering that the route or plan has to be altered, like in real life. That said, IIRC if you use nav mesh route plotting then I think the routes will avoid large rock areas, I could be wrong though.
  18. If you can tell me a coordinate on the map then I can look into it. However... a) The map/terrain is supposed to be intentionally slow, otherwise the government force can cover the entire map in half the scenario's time. b) Vehicles are not intended to drive up the mountains, so there are terrain types that I think prevent them from driving forward (rocky type). c) Soft sand is intentionally slow. Outside of that, I can make some adjustments if there is a mistake made in a particular place.
  19. Thanks, it should be fixed in the next update.
  20. 13 OCT scenario: Civil War Dera Ghazi-4019a SPECIAL CONSIDERATIONS: THREE COs are needed. Blue vs. Orange vs. Red. Blue and Orange (both insurgents) are neutral at the start, both against Red (which is a very large/powerful government force). However only one side can win, Orange and Blue will be enemies at some point. Draft? No. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules.
  21. Are you saying it does destroy a vehicle in game? I guess it would depend on what vehicle and where you shot it at (roof or side lower hull). The "M383" in SB has some significant explosive power. Any kill would not be from the HE effect, not the KE penetration of the round.
  22. 06 OCT scenario: Hasty Defense 01 (DE) Leo1A4-HTH-MAD-4010c SPECIAL CONSIDERATIONS: Draft? No. NOTES: Avoid studying the enemy's side; only gather intel from the briefing and exposed enemy unit icons (enemy intel), and briefly looking over both sides to figure out which one you want to CO. Anything beyond that ruins the fog of war element. To avoid passwords, open the scenario in Network Session as HOST and choose the side you want to play and go to planning phase. You may briefly look at both sides like this to see which side you want to play or CO on. As CO, once you choose a side, go to that side and create your plan. Remember to play within the TGIF House Rules and SB.com community rules.
  23. OK, in the next update the M2/M3 should be able to assign KE or HE to either ammo slot, or both.
  24. OK thanks, good to know. I will see what we can do...