There are 20-30 PMCs spawning at fortress on customs, all of the POIs on Shoreline, Scav Camp on Woods, and many other POIs and I end up fighting armies just to finish one task. Im not sure if this is a feature I can turn off, as far as them teaming up, I thought I was just getting really unlucky at first, but after the 5th or 6th time getting gangbanged by BEARs, I'm just gonna try to reach out for help to see if theres any sort of solution here.
Posts by TMAC02
-
-
Alright so idk what changed but i did it again and it worked soooo hell yeah
-
I had to get the patcher files emailed to me because my wifi couldnt connect to the website
-
The issue I'm having with the installer is that I think its trying to grab the files from a separate location and my internet doesnt have the bandwidth to handle it. I tried to use the installer and it just created a zip folder with nothing in it, so I had to do it manually. I've had SPT on a different computer before, so I have a vague understanding of what I'm doing.
-
Alright so looking in the SPT file, there is no folder labeled logs. maybe it would be nestled somewhere else, but I cant follow that path. When I go into BepinEx, theres no log output there. I got config, core, patchers, and plugins, and none of those have any logs. The server log I could find and put in, however.
-
I can open the server, and the launcher, and create a profile with no problems, but when I hit start game the button just goes black and nothing happens. also upon further investigation, it would appear some of the logs are not where the website says they are, as i looked and couldnt find them. not sure if that was user error or something else.
-
-
Im on a public wifi network trying to get the patcher installed and i believe their website doesnt allow public connections, as i waited for upwards of 30 minutes to get a connection to no avail. I was just wondering if there was another way i could get the files that did not require me to go to the website. I can navigate most other websites fine, so far only had issues with these websites.
-
Thank you! I'd probably be happier with someone else helping me, I thought the courses I've taken would have made me qualified enough to handle something like this, but clearly not. I just joined the server, should i dm you on that or?
-
Originally had Slot stackslot cartridges in item error with id effa6a6b7ad6358aba961f29 and read in another post to go to the profiles tab and remove all instances of that id, i tried, and now whenever i tried to load the server i get
(node:13928) UnhandledPromiseRejectionWarning: Error: Unsupported issue: Expected string but "{" found. (please open an issue at the repo)
at runFixer (C:\Battlestate Games\TarkovSP\node_modules\json-fixer\index.js:91:16)
at fixJson (C:\Battlestate Games\TarkovSP\node_modules\json-fixer\index.js:103:21)
at doubleCheck (C:\Battlestate Games\TarkovSP\node_modules\json-fixer\index.js:29:44)
at fixJson (C:\Battlestate Games\TarkovSP\node_modules\json-fixer\index.js:105:10)
at fixingTime (C:\Battlestate Games\TarkovSP\node_modules\json-fixer\index.js:113:11)
at checkJson (C:\Battlestate Games\TarkovSP\node_modules\json-fixer\index.js:146:12)
at JsonUtil.deserialize (C:\Battlestate Games\TarkovSP\obj\bundle.js:16938:99)
at SaveServer.loadProfile (C:\Battlestate Games\TarkovSP\obj\bundle.js:15062:50)
at SaveServer.load (C:\Battlestate Games\TarkovSP\obj\bundle.js:15022:39)
at SaveCallbacks.onLoad (C:\Battlestate Games\TarkovSP\obj\bundle.js:2609:25)
(Use `Aki.Server --trace-warnings ...` to show where the warning was created)
(node:13928) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.htm…unhandled_rejections_mode). (rejection id: 1)
(node:13928) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code
