feel like the global tasks sweep strat should probably be nerfed somehow. my thought would be, give each team an individual ten minute overall cooldown on global task claims. that is to say, a certain team can only claim one global task per ten minutes. say, deliver gas masks, and then in ten minutes you're allowed to deliver tea, and then after another ten minutes you can claim hot chocolate.
another teams would be able to claim a global task for bananas during this time, and their own ten minute cooldown would start.
(the global tasks can either keep their individual ten minute cooldown [i.e. after tea is claimed no one else can claim tea for ten minutes] or a slightly shorter cooldown, say 5-7 minutes)
when a global task is claimed, everyone is notified, right? if not, in my hypothetical, they will be.
then, a team trying to sweep six tasks at once would actually take sixty minutes to do, allowing another team to swoop in and have a chance to stop it in cinematic, entertaining fashion rather than tubbo having to grind resources and then log out in front of the merchant to counter this, which is boring for everyone (including the person delivering). plus, if a team cuts it down to the last second and ends up getting delayed, they physically wouldn't have time to make a delivery, meaning even being a BIT of a nuisance could be a viable strategy, even if you can't manage to kill; if you can STALL you could still wreck their plans.
that's my dream anyway idk i'm not a game designer. just think it would be interesting for most players
(i elaborate under)
red team would have to shake up their strategies, which is fun since they're a team that kinda has to rely more on strategy than outright brawn (overall the team's pvp can't be relied on unless they have carre or phil, as seen today when pierre, bad, and etoiles attacked phil cellbit foolish and baghera, and cellbit and foolish both died to etoiles in the attack, despite it being a 4 on 1 at the time. baghera was killed by bad soon after. phil was the one to get the kills. the first day, when blue attacked [niki, tubbo, and bad as i recall] carre got both kills)
the other teams would then still have a way to stop a global sweep since a sweep would have to start earlier, allowing not only more time to arrive at global to pvp about it, but ALSO allowing another team to swoop in and steal the goal out from under the team again
i'm gonna use it in a scenario bc i'm badboyhalo and i can't stop myself from making examples:
so, tonight, if the proposed cooldown was in place, bad and tubbo would both still had roughly 17 minutes when red team would have HAD to start the sweep process if they wanted all six global tasks: 1 hour until the server closed at absolute MINIMUM. more for safety's sake.
therefore, in this scenario, there's a lot to happen
blue team could wait at globals, knowing red will probably try this strategy, and attempt or perhaps SUCCEED in killing red. if they kill red entirely, the operation is a wash; red doesn't have to gear to come back from scratch and take out blue team, and even if they could, the travel time to return to globals alone would mean they wouldn't get all the global tasks, potentially meaning they don't take the lead. if blue team is unable to kill red and dies themselves or has to retreat, but succeeds in delaying red, red would face the same problem.
if red sends in all of the task items on one person, and that person dies, even if the rest survived, blue could loot the items from that person and would be able to either use the items themselves, if green is currently the owner, or could run away with the items, effectively wasting red's time and again, meaning they wouldn't get all tasks claimed even if they were able to overtake the runner and reclaim their items.
i'm unclear what would happen if red divided the task items between them since it seems like the person claiming the task doesn't have to have all (or any? again, unclear) the items in THEIR inventory in order to claim so long as a teammate is nearby with the items in their inv (evidence: pac's vod "voltei... o que tá acontecendo no QSMP?!" at roughly 3:00:00; tubbo claims tea and tea is taken out of pac's inventory. i don't know the limits of this strategy)
blue team also has time to swoop in and steal a global task out from under red during this time. say, if red team had claimed the task for 10 tea leaves, upping the price to 15 tea leaves, and then blue team snuck in and claimed the task and set the price up to 20 tea leaves, (since the proposed 10 minute cooldown on claims would be TEAM LIMITED; red's cooldown applying to red only and so on). if red waited until the last second, they wouldn't have the time to reclaim this task even if they did have the resources, possibly forcing them to start their sweep earlier to counter this possibility, at which point team members who had logged on earlier and are out of time by the end of the night, OR members who live in time zones that don't allow them to stay up until server close, may have an easier shot at participating in defending against a global sweep.
all of this DIRECT CONFLICT would make for good audience entertainment and heighten the stakes of an attempted global sweep, since it would practically have to be one team defending globals for an hour while they pipe all their resources into it, knowing that if they die another team could easily swipe their task resources and use it themselves (along with the rest of their gear). it makes it more interesting, while still mostly viable.
plus it would force more strategizing for red team which is maybe just a personal plus, i just really like seeing people planning both in advance and in spur of the moment. it's really satisfying to see how a plan comes together and succeeds or fails; plus, since red team is the main team using this strategy at the moment and their main draw and strength as a team is cohesion and communication this would be completely fucking riveting for me as a viewer so maybe this is just a personal thing. but i really really think it would be fun
but again, i'm not a game designer, or a qsmp player, or a qsmp admin, or honestly even really a gamer? so maybe i'm off my rocker and out of my gourd and this isn't viable or balanced in any way shape or form but YKNOW what is this blog except putting stupid thoughts into the void and seeing if this time the void spits back hate mail so. i'm folding this into a paper airplane and throwing it into the abyss. hopefully it made sense.
k love you appreciate you getting this far, have a good week!!
(i hope your team gets a win in dramatic fashion and celebrates together!!! i hope they come together and unleash a plan so spectacular it takes the server by storm!!! i hope it's so good it becomes a vod you go back to even years in the future!!!! i hope you have a good week!!!!!)
29 notes
·
View notes
@fatmaninalittlesuit wants to see friends and their pets today.
Check it out, I'm bald as fuck!
And Soba has the crazies!
I went to the salon (and straight home). I was nervous asking the stylist for 00 all around, since stylists don't typically like shaving women's heads, but she was super cool about it.
I told her, "I want it gone. I want to go as long as possible without having to do my hair."
She said, "What about this 000 guard, then? It'll buy you another week or two?"
Yesplz!
She also recommended some clippers for me (the exact ones I bought), and told me how to sharpen and oil them. So I'll be doing that sometime before like December when my hair comes back lol.
Time to play with Soba.
50 notes
·
View notes
Tag people you want to know better
I was tagged by @lusavors ✨
• last song: Mermaids by Florence and the machine; tuta gold by mahmood
• currently watching: YouTube, gameplays and artist’s vlogs mostly… does it count?
• three ships: hannigram (it has it’s own set of problems but love me some murder husbands) from Hannibal; Anastasia/Dimitri from the animation movie Anastasia (he starts as an asshole but he grows on you) and Tiana/Naveen from the princess and the frog. Talking if’s violet/seven and equally violet/orion from Infamous; A/Crown from a tale of crowns; m/detective from whc and jax/merc from rywd
• favorite color: yellow
• currently consuming: camomile tea
• place of birth: italy
• current location: italy
• first ship: don’t remember but let’s say it’s minako/ren from strobe edge manga
• relationship status: single like a pringle
• last movies: i am the pretty thing that lives in the house
• currently working on: like on this blog or generally? lol
I’m trying to move out and working on my children’s book portfolio. Also dipping my feet into comic and destressing by playing some games on my free time (it’s not really working haha)… on here i’m planning on posting some ifs sketches and stuff from other games I’m enjoying 🤞🏻
tagging @womenenthusiast2 @amyreads @artsyaprilmr @capricule and whoever feel like doing this!
6 notes
·
View notes
"Vulkan is weird— but it's weird in a way that makes a certain sort of horrifying machine sense. Every Vulkan call involves passing in one or two huge structures which are themselves a forest of other huge structures, and every structure and sub-structure begins with a little protocol header explaining what it is and how big it is. Before you allocate memory you have to fill out a structure to get back a structure that tells you what structure you're supposed to structure your memory allocation request in. None of it makes any sense— unless you've designed a programming language before, in which case everything you're reading jumps out to you as "oh, this is contrived like this because it's designed to be easy to bind to from languages with weird memory-management techniques" "this is a way of designing a forward-compatible ABI while making no assumptions about programming language" etc. The docs are written in a sort of alien English that fosters no understanding— but it's also written exactly the way a hardware implementor would want in order to remove all ambiguity about what a function call does. In short, Vulkan is not for you. It is a byzantine contract between hardware manufacturers and middleware providers, and people like… well, me, are just not part of the transaction.
Khronos did not forget about you and me. They just made a judgement, and this actually does make a sort of sense, that they were never going to design the perfectly ergonomic developer API anyway, so it would be better to not even try and instead make it as easy as possible for the perfectly ergonomic API to be written on top, as a library. Khronos thought within a few years of Vulkan being released there would be a bunch of high-quality open source wrapper libraries that people would use instead of Vulkan directly. These libraries basically did not materialize. It turns out writing software is work and open source projects do not materialize just because people would like them to."
15 notes
·
View notes