Jump to content

Stanhope

Spartan
  • Posts

    2,130
  • Joined

  • Last visited

  • Donations

    20.00 GBP 

Everything posted by Stanhope

  1. AW MVP 2023: @MidnightRunner AW Most Friendly Admin/Moderator/Spartan 2023: @JJ Cakes AW Most Helpful Admin/Moderator/Spartan 2023: @MidnightRunner AW Most Active Staff Member 2023: I'm not active enough to know this :) AW Strictest Staff Member 2023: AW Best Team Player 2023: AW Most Helpful Member *Non Staff* 2023: AW Most Friendly Member 2023: @Nibbs AW Tacti-cool member 2023: AW Underrated Member 2023: AW Most Incoherent Member 2023: @Rickard AW DAAASSS BOOOOT 2021 - The drunkest member of 2023: AW Best/Worst Pilot 2023: AW Best Voice 2023: AW Funniest Person on Team Speak 2023: AW Worst Joke 2023: @LH5 AW Best Moment 2023 (can be in-game, on Teamspeak or Forum): AW Best Forum Post 2023 (please put URL in): AW Dankest Meme Post In Discord 2023: AW Best Driver 2023: AW Worst Driver 2023: obligatory @Xwatt AW Best Fail 2023: AW Best Ban of 2023: AW TeamSpeak Channel 2023: AW Best Screenshot 2023: AW Best/Worst Call-out 2023: AW Candidate for the Hague 2023: @Rickard AW Role Model 2023: AW Best Shot/Worst 2023:
  2. You're probably having the same issue as this person:
  3. There is technically a way to script in this behaviour but it's not something that's written and tested in an hour. There's probably a lot of edge cases I can't even think of right now
  4. Whigital and me (but mostly Whigi nowadays, less so me) are they, we (but mostly Whigi) maintain I&A 3
  5. To the best of my knowledge we don't do anything intentionally to stop you from de-pboing the mission file. That being said I've just tried it myself and am also getting an error (a different one though). I can't give you a copy though as I only have an as of yet unreleased version of I&A, I don't have access to the 3.4.22 version (and I'm not hand out a version we haven't released yet for someone else to run )
  6. AW MVP 2022: AW Most Friendly Admin/Moderator/Spartan 2022: @MidnightRunner AW Most Helpful Admin/Moderator/Spartan 2022: @MidnightRunner AW Most Active Staff Member 2022: @chicken_no6 AW Strictest Staff Member 2022: AW Best Team Player 2022: AW Most Helpful Member *Non Staff* 2022: AW Most Friendly Member 2022: @Nibbs AW Tacti-cool member 2022: AW Underrated Member 2022: @GhostDragon AW Most Incoherent Member 2022: @Toasted_Bread_Slice AW DAAASSS BOOOOT 2021 - The drunkest member of 2022: AW Best/Worst Pilot 2022: AW Best Voice 2022: AW Funniest Person on Team Speak 2022: AW Worst Joke 2022: AW Best Moment 2022 (can be in-game, on Teamspeak or Forum): AW Best Forum Post 2022 (please put URL in): AW Dankest Meme Post In Discord 2022: AW Best Driver 2022: AW Worst Driver 2022: AW Best Fail 2022: AW Best Ban of 2022: AW TeamSpeak Channel 2022: AW Best Screenshot 2022: AW Best/Worst Call-out 2022: AW Candidate for the Hague 2022: @Rickard AW Role Model 2022: AW Best Shot/Worst 2022:
  7. For the opfor thing go to I believe general settings in the editor, faction relations are defined there. For the marker, are you sure you copy pasted it over? We move ome marker around, we don't create a new one every time
  8. Depending on the type different things will spawn, it's not fully implemented. I believe the function for that is in functions/ao/spawnAoSpecificItems or something like that
  9. I'm sure that if someone provides I&A3 ready to play on Western Sahara core staff will happily put it on the server
  10. The FOB will spawn once that AO that's in the same location has been completed
  11. Yes, once that FOB is captured it'll spawn one of those helicopters, and every time it respawns it'll pick a random one again iirc
  12. The options I found weird in the server startup params are "-O=0 -H=0", I don't know what these do. I also don't know how you're able to run a mission that's not packed into a pbo but yes, something could've gone wrong with the packing causing the mission not to boot.
  13. I don't see anything wrong with that rpt either except for some unusual server startup parameters, I'll test if I can boot a server with the version from the server with the include commented out later tonight (if I don't forget) to be sure.
  14. Could we get the legstraps (backpack version)?
  15. If an AO is 500 meters away from an FOB and there's no way for a helicopter to take off because of the AA threat in said AO the current rule allows pilots to jump into a hemtt transport and drive people to the AO. Your suggested rule change explicitly forbids this.
  16. Someone, I don't know who, forgot to ask for suppressors for the Scars so: Out of curiosity did any of the stingers (rhs_weap_fim92, rhs_fim92_mag) that were presumably in that c-130 end up in the hand of the guerilla?
  17. Some stuff I wouldn't mind having in the arsenal if it doesn't clog it up:
  18. I can think of nicer ways to start of my weekend but here we go. Our current fog control script has been in place since at least 16/05/19. I wrote it some time before that. Could've been a year before that could've been a day, I don't know. What I do know is that I find it extremely concerning that something that I put in place almost 3 years ago is supposedly always broken. So I looked at said script a bit more to see if there may be a bug in it. Here's how it works right now: The script runs every give or take 360 seconds (6 minutes for reference). It starts by removing any fog decay and the fog base (aka it makes the fog of equal density at all altitudes). It then check if the fog is above a level of 0.7 (fog in arma can be in the range of 0 to 1). If it's above .7 it'll, over the next 40 seconds reduce, the fog value to 0. If the fog value is above 0.4 it'll, over the next 40 seconds reduce the fog value to 0. So effectively the max amount of fog that can be on the server for more than 6 minutes is 0.39. So River, what do you think is an acceptable max value for the fog? If you want to change it from 0.4 to any other value, could you provide some reference screenshots what that'd look like in game for the value(s) you suggest?
  19. TFAR (used on our AWE server) doesn't have a discord plugin.
  20. The mission saves its own state after every AO (and only saves AO progression btw) (assuming the persistence option is turned on). If after a restart this progression is lost your server host most likely deletes the server's profile file (can't remember the exact name of that file and I'm at work so can't check). To try you can run this code before a restart (server side in the debug console when you're logged in as admin): profileNamespace setVariable ["ThisIsATest", "HelloWorld"]; saveProfileNamespace; And after restart: hint str(profileNamespace getVariable ["ThisIsATest", "Didn't work"]); If a hint shows with "helloWorld" then there's a problem with the mission saving things, if it shows "didn't work" then the profile file got deleted.
  21. That file has .pbo twice, remove one. Next you have zeusAdminUIDs = [rapha]; in your initserver, that should be zeusAdminUIDs = ["PutYourSteamUIDHere"]; (replace PutYourSteamUIDHere with your steam UID, make sure you have " around it). If both of those are fixed and it still doesn't work please share your server RPT (typically found in: C:\yourUser\AppData\Local\Arma 3).
×
×
  • Create New...