How to solo a strike?

[HazMat]

So, i've put my fireteam as CLOSED, and still when I start a strike its searches for players and puts me in a group.
I don't want that, since i just want to finish a quest that requires 150 kills.

[Mister Wiggles]

You can't in game, there are no real ways of doing it. You can however mess around with network stuff so no one can match make with you. I'm sure you can google that though if you're interested because I havent the foggiest.

[Huzaks]

Just hop in lost sectors while doing the strikes to get easy kills

[Mister Wiggles]

Originally posted by huz:

Just hop in lost sectors while doing the strikes to get easy kills

No, don't do this. Ruins the strike for the other people and if they know what they are doing they can pull you out of the lost sector by wiping.

Look into the network side of things or maybe get some friends/lfg players. Its 150 kills, its like 2 strikes man.

[Hunter]

You can just start for exampe the strike "lake of shadows" on earth which has a open world starting lobby and farm for some kills in public events. Thats how i do it when i have to complete some strike quests

[Nibbie]

You can try a nightfall, those don't have matchmaking.

[Nordblut]

@OP people are saying if you get your powerlevel below 750 then you won´t be matched with others.

[LeaphyMoon]

Legit just go into a nightfall and set it to where there is no match making and go in and farm your kills. Enemies will pack a lunch but you'd do it solo

[HazMat]

Originally posted by huz:

Just hop in lost sectors while doing the strikes to get easy kills

well, the reason Im asking this is because I didnt want to be a dbag to other ppl doing the srike, exactly by going into lost sectors while others progress

[HazMat]

Originally posted by Nibbie:

You can try a nightfall, those don't have matchmaking.

Oh, Ok, I'll try that

[Natjur]

Or just have 3 accounts so you can solo anything on easy level

[MrJane]

After Destiny went F2P, I actually set up my kid's PC and my wife's with the game and made a fire team with their accounts, then just left them behind and did all my bounties/quests. I know, not everyone has access to 2 other PC's, but it's a round about way of doing it if you really want.

I also had to do the tutorial 2 more times, but it was just that one time.

[HazMat]

Nightfalls did the trick, thanks all.

[LiL'LuPeY^]

for those interested, found on Reddit.
A script that closes all destiny ports this way you can solo anything.
Also helps to load faster into the tower since you don't have to connect to other players.

Copy & paste it into powershell.exe or save it as a .sp1 file to simply run it.

if (!([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) { Start-Process powershell.exe "-NoProfile -ExecutionPolicy Bypass -File `"$PSCommandPath`"" -Verb RunAs; exit }
New-NetFirewallRule -DisplayName "Destiny2-Solo-1" -Direction Outbound -RemotePort 27000-27100 -Protocol TCP -Action Block
New-NetFirewallRule -DisplayName "Destiny2-Solo-2" -Direction Outbound -RemotePort 27000-27100 -Protocol UDP -Action Block
New-NetFirewallRule -DisplayName "Destiny2-Solo-3" -Direction Inbound -RemotePort 27000-27100 -Protocol TCP -Action Block
New-NetFirewallRule -DisplayName "Destiny2-Solo-4" -Direction Inbound -RemotePort 27000-27100 -Protocol UDP -Action Block
Write-Host "Destiny 2 Solo mode activated.  Press any key to deactivate solo mode."
Read-Host
Remove-NetFirewallRule -DisplayName "Destiny2-Solo-1" 
Remove-NetFirewallRule -DisplayName "Destiny2-Solo-2" 
Remove-NetFirewallRule -DisplayName "Destiny2-Solo-3" 
Remove-NetFirewallRule -DisplayName "Destiny2-Solo-4"

[Zoomii]

Originally posted by Ger LuPeY^:

for those interested, found on Reddit.
A script that closes all destiny ports this way you can solo anything.
Also helps to load faster into the tower since you don't have to connect to other players.

Copy & paste it into powershell.exe or save it as a .sp1 file to simply run it.

if (!([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) { Start-Process powershell.exe "-NoProfile -ExecutionPolicy Bypass -File `"$PSCommandPath`"" -Verb RunAs; exit }
New-NetFirewallRule -DisplayName "Destiny2-Solo-1" -Direction Outbound -RemotePort 27000-27100 -Protocol TCP -Action Block
New-NetFirewallRule -DisplayName "Destiny2-Solo-2" -Direction Outbound -RemotePort 27000-27100 -Protocol UDP -Action Block
New-NetFirewallRule -DisplayName "Destiny2-Solo-3" -Direction Inbound -RemotePort 27000-27100 -Protocol TCP -Action Block
New-NetFirewallRule -DisplayName "Destiny2-Solo-4" -Direction Inbound -RemotePort 27000-27100 -Protocol UDP -Action Block
Write-Host "Destiny 2 Solo mode activated.  Press any key to deactivate solo mode."
Read-Host
Remove-NetFirewallRule -DisplayName "Destiny2-Solo-1" 
Remove-NetFirewallRule -DisplayName "Destiny2-Solo-2" 
Remove-NetFirewallRule -DisplayName "Destiny2-Solo-3" 
Remove-NetFirewallRule -DisplayName "Destiny2-Solo-4"

I used a solo script a few months ago, it may have been this one. I stopped because, while it's unlikely they would ban you for it, it does go against TOS and they could theoretically ban you if they wanted.

[Mister Wiggles]

Originally posted by Zoomii:

Originally posted by Ger LuPeY^:

for those interested, found on Reddit.
A script that closes all destiny ports this way you can solo anything.
Also helps to load faster into the tower since you don't have to connect to other players.

Copy & paste it into powershell.exe or save it as a .sp1 file to simply run it.

if (!([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) { Start-Process powershell.exe "-NoProfile -ExecutionPolicy Bypass -File `"$PSCommandPath`"" -Verb RunAs; exit }
New-NetFirewallRule -DisplayName "Destiny2-Solo-1" -Direction Outbound -RemotePort 27000-27100 -Protocol TCP -Action Block
New-NetFirewallRule -DisplayName "Destiny2-Solo-2" -Direction Outbound -RemotePort 27000-27100 -Protocol UDP -Action Block
New-NetFirewallRule -DisplayName "Destiny2-Solo-3" -Direction Inbound -RemotePort 27000-27100 -Protocol TCP -Action Block
New-NetFirewallRule -DisplayName "Destiny2-Solo-4" -Direction Inbound -RemotePort 27000-27100 -Protocol UDP -Action Block
Write-Host "Destiny 2 Solo mode activated.  Press any key to deactivate solo mode."
Read-Host
Remove-NetFirewallRule -DisplayName "Destiny2-Solo-1" 
Remove-NetFirewallRule -DisplayName "Destiny2-Solo-2" 
Remove-NetFirewallRule -DisplayName "Destiny2-Solo-3" 
Remove-NetFirewallRule -DisplayName "Destiny2-Solo-4"

I used a solo script a few months ago, it may have been this one. I stopped because, while it's unlikely they would ban you for it, it does go against TOS and they could theoretically ban you if they wanted.

Yeah hence why I mentioned it was a thing but had the awareness to not post a link to it. Its network manipulation which is ban worthy