Please enable revives for inactive mission targets.
Many inactives have revives disabled. If they're a popular mission target (especially for hosping missions) this creates a logjam and limited resource, as players compete to get their hits in.
I'm willing to spend e to shortcut that process, as currently the target is in hospital for 3 days straight.
Yes I can set a timer, but often, I can't be available when the timer is up, which reduces my ability to complete the mission down to just getting lucky - not a good gameplay mechanic.
The reasons I'm aware of to have revives disabled was to avoid chain mugging (which doesn't apply any more with recent changes to mugging) or revives in a war (doesn't really apply for an inactive) or just to avoid other players being annoying (again, doesn't apply to an inactive)
The only possible reason I can think of to leave revives disabled, would be in case the player comes back and wants it that way for any reason. In this case the fix would be to disable revives again when they next log in.
CT in its basic format feels extremely tedious and frustrating to play. Long, slow walks, with occasional randomised restarts. An object lesson in how to waste player time, through the power of the sunk cost fallacy.
So here we have an ingame item, to make the game less tedious to play, which you get by playing the tedious game as a reward.
Someone needs a proper battering with the game design clue stick.
So we have the potential for material harms - data loss due to running out of storage, high volumes of writes leading to wear on consumer components (a second avenue of potential data loss) and unnecessary repair costs for players who simply aren't aware this is a Torn problem (whatever percentage of players who do not read GD etc.)
The vote is null and void if players are suffering material harm, that was not known at the time of the vote - we can't have players voting in favour of something that will harm other players. Also I wasn't aware there was a vote.
No matter what Sendbird's response, this doesn't absolve devs here - they chose the component/team, and they didn't sufficiently test it before pushing the release prematurely.
Add an extra line of code to exempt test accounts from award triggers? Because presumably there will be future test accounts which will break or make trivial something unexpected...
The idea that maybe, one day, Ched might still come out with some new feature that gives me another clean hit of the original crack cocaine this game was built on. That private island where I wait might as well be a cardboard box under a bridge.
Joined, attacked, stalemated, stalemate button didn't do anything. Refreshed, and joined queue. Counter went down smoothly and got a second round. Attacked, Stalemated and stalemate button again did nothing. Refreshed, saw the Join Queue button repeatedly flash for microseconds. Refreshed again and Joined Queue. Piñata sadly died before countdown completed.
Suggestion - remove the two confirmation prompts to change a car when racing. Both are silly for what are zero cost actions with no negative consequences, since you can just change again if you pick the wrong one.
Change this Car? Yes No
Are you sure you want to change your current car to Trident?
Are OCs going to be time sensitive i.e. requiring players to online at certain times?
Fine with the 'easy money' aspect being removed from OCs, but it's a fine balance - make it too arcane/demanding/opaque and that's just a nerf in disguise.
If a faction migrates to 2.0, and decides after some experimentation it's another Chedburn special, can they move back to 1.0? Or a one way jump into the fog?
Almost 4 years later, we have no changes, players still pile on to unrevivable mission targets. This is still frustrating, totally unnecessary, and the opposite of fun for anyone getting one of these missions.
1%? If the forum had that level of engagement (hint: it won't, and we know it) there would be more suggestions, posted at a faster rate, and individually receiving less attention, except (again) the tentpole ideas which receive widespread enthusiasm and lots of bumps. So basically a recipe for killing all smaller tweaks no matter their individual merits, which was exactly my point.
Additionally, many of these suggestions are just obviously good ideas, but ultimately very small changes - not tentpole ideas that are going to receive widespread enthusiasm, or an idea that merits a large marketing campaign. But, they would nevertheless be great for the game. Having a hard 250 votes limit before devs will even consider them it is silly, and I'd say it damages the game.
Dull, merges with the background, difficult to differentiate from everything surrounding it. It should be possible to glance in that direction and tell exactly what the tab is for, but instead it's more difficult. The previous favicon was crap, but it did have the advantage of being distinctive.
I'd already blocked what I could with Ublock Origin (using the element picker, I ended up with www.torn.com##.no-zalgo in the custom filters, as well as sendbird.com but clearing the cache again helped as well. I've now added sendbird.com to the hosts file, no idea if that will also help.
I'm still sometimes seeing the chat window appear briefly then disappear so there's something else to block still.
I'm also seeing errors in the console - some aspects of Torn seem to be panicking about what I've blocked so far :)
[edit] yes there's definitely something else to block as the IndexedDB\sendbird\NestDBStore is quickly repopulated after clearing it.
Anyway, seems like a better solution would be a server side toggle. I'm not going to hold my breath on that though given Ched's previous inclinations - e.g. the annoying cache opening animations he was so pleased with
So, the bulk of the browser cache usage for me wasn't, to my recollection, in the _testMozilla folder - and why would it be on a Chromium based browser (well, Chrome)? That would be silly (perhaps it was just a silly bug though?)
There's still confusion about what was being stored, and why - initially it was 'log data' and now it's a cache? Which?
Still seeing lots of lag, though I'll admit that may at least partly down to my PC being a potato.
Perhaps I just don't meet the minimum requirements for a text based browser game any more? So what's the recommended minimum spec for a PC to play Torn nowadays, to guarantee frame rates above, say, 2 per second?