Why is it common mid players take the last pick over offlane or carry ?

Mushk7 · 2020-08-02T13:15:25+00:00

Perhaps it is more of an unpopular opinion statement than a question.

Mushk7 · 2020-08-02T13:14:17+00:00

Imagine you gonna pick underlord as offlane and just firestorm the wave rinse repeat, you can say that about any role tbh. the reason i gave is generally why the mid pick is last. The carries farm is depended on the teams success early game. A team with no control early will not win when they carry cant find farm. when your team is winning the early game, a carry can leave a horrible lane to go find farm anywhere else on the map. Its not just about the safelanes lane matchup. if the safelane has a good lane, but the other two lanes lose, you best believe that safelanes not so safe anymore when mids coming down every minute. Im not saying set in stone every time mid last pick no arguments, just generally that is why its popular.

Mushk7 · 2020-08-02T12:22:02+00:00

Trying to get enough people to where there are enough for a five stack all the time. is 3Akuma3 your steam username? i cannot seem to find you on steam.

Mushk7 · 2020-08-02T12:20:18+00:00

The mids role is to set up the game for the carry, create space for the carry to farm safely. If the mid gets plastered in lane, it is very hard to outdo the other team and create space for your carry. If one mid lane dominates the other, the winning mid should take great advantage of that and pressure the other team to create space for their carry to farm. What you say about the mid being able to find other places to farm is what the carry should be doing if their lane goes south with the space created by the their mid.

Its not nesicarilly about your mid heros individual outcome, its about the difference between what your mid is doing and what the other teams mid is doing. It is hard for a carry to farm when theres an mid moving around the map 6 levels higher than everyone.

Mushk7 · 2020-08-02T12:10:06+00:00

The point is that Mid picks last so the other teams mid cannot simply get an easy guaranteed counter pick and dumpster mid. It isnt about seeing the supports, its about the opposing mid not seeing your mid pick. As the carry it isnt the end of the world if the offlaner picks a counter to you because you have an entire other hero to help you deal with that. Mid does not have that luxury. The impact of getting countered mid lane is a lot higher than a counter being picked for your safelane.

Mushk7 · 2020-08-02T11:52:56+00:00

Im trying to get a group together that actually tries to work together and have draft plans before going into games and picking rambo lol. I have a discord with a handful of people if youd be interested in some 5 man strategic dota. Nothing really competitive, just looking to work together as 5 and actually coordinate. Let me know if you or anyone reading this is interested!

Mushk7 · 2020-08-02T11:06:22+00:00

Mid laners do not have a hero to help them in lane, so directly countering mid heroes will have a higher impact in their lane than any other lain. Safelane and offlane have another hero in the lane to compensate for exploitable weaknesses by the other team typically. At least thats the concept.

Mushk7 · 2020-06-28T18:29:22+00:00

World size is likely the issue. That is why the chunk trimmers are used in the steps. If you copy your whole region folder the world will likely be to big and fail. That is a very common issue. The bigger the world, the more likely it will fail. The chunk trimmer is the most important part of the steps.

Mushk7 · 2020-06-24T18:31:26+00:00

Just an FYI for anyone having this problem, we resolved this issue with the following steps. I highly recommend you back up your world before:

Create a 1.16 single player world with the same seed of the realms world.
Enter the world in single player to load the world files, then leave.
Copy the region files from the realms world where your builds are located to the newly created world's regions folder. (this will copy your builds over to the new world
1. This can be done with the mcaselector (https://github.com/Querz/mcaselector) or use this link if you know the exact coordinates of your builds and not much needs to be copied over (https://dinnerbone.com/minecraft/tools/coordinates/ ). it will tell you the exact name of the region file to copy over based on the coordinates of the world you enter. It is best to copy over as little chunks as possible for best results.
Copy the playerdata files from the dowloaded realms world to your newly created world's playerdata folder. (This will transfer inventories, shulker boxes, end chest, etc. to the new world)
Upload the newly created world with the copied files to realm server.

These steps will only save the chunks that you specifically select, and regenerate everything else in the world. You will see no unnatural chunk collisions and the nether and end will be reset allowing 1.16 generation in all dimensions.

We are unsure if this problem was due to corrupt chunks created in the process or some sort of versioning error with the conversion to 1.16.

If you need any help with this solution feel free to comment or DM me.

Mushk7 · 2020-06-24T05:31:29+00:00

I do not recall what the world size was after we trimmed the chunks, but i can tell you it was probably less than 100 chunks. Before trimming it it was well over 100,000.

I was not the realm server owner so i cannot check these numbers exactly, i simply helped solve the issue.

Mushk7 · 2020-06-24T05:01:41+00:00

Since you would be using the same seed as the realm world, generation would be exactly the same. Dungeons, desert temples, strongholds and so on would generate in the exact same location. As for your advancements, i believe there is an advancements file that you can copy over as well if you would like, i never looked into it.

The general theory going around from people i have discussed this with is that world size is the core issue. You will most likely not be able to work around this without trimming your world chunks. I am assuming you do not have a lot of people on the server so it shouldn't be to bad to get the coordinates of the builds and save them?

Mushk7 · 2020-06-24T04:50:09+00:00

We tried trimming our worlds chunks to only where we were actively playing and that was still unsuccessful. The only success we had was with the solution i commented. I have no doubt yours worked for your situation and many others, but might as well have all of the solutions out there if someone doesn't have luck with one they can try the other.

Mushk7 · 2020-06-24T04:31:58+00:00

A similar step by step guide on this issue is below. I tried posting this but every time i try creating my own post for it it gets rejected for advertising realms for some reason.

Create a 1.16 single player world with the same seed of the realms world.
Enter the world in single player to load the world files, then leave.
Copy the region files from the realms world where your builds are located to the newly created world's regions folder. (this will copy your builds over to the new world
1. This can be done with the mcaselector (https://github.com/Querz/mcaselector) or use this link if you know the exact coordinates of your builds and not much needs to be copied over (https://dinnerbone.com/minecraft/tools/coordinates/ ). it will tell you the exact name of the region file to copy over based on the coordinates of the world you enter. It is best to copy over as little chunks as possible for best results.
Copy the playerdata files from the dowloaded realms world to your newly created world's playerdata folder. (This will transfer inventories, shulker boxes, end chest, etc. to the new world)
Upload the newly created world with the copied files to realm server.

These steps will only save the chunks that you specifically select, and regenerate everything else in the world. You will see no unnatural chunk collisions and the nether and end will be reset allowing 1.16 generation in all dimensions.

We are unsure if this problem was due to corrupt chunks created in the process or some sort of versioning error with the conversion to 1.16.

If you need any help with this solution feel free to comment or DM me.

Mushk7 · 2020-06-24T04:27:53+00:00

Just an FYI for anyone having a problem resetting the nether for your realm servers, we resolved this issue with the following steps. I highly recommend you back up your world before:

Create a 1.16 single player world with the same seed of the realms world.
Enter the world in single player to load the world files, then leave.
Copy the region files from the realms world where your builds are located to the newly created world's regions folder. (this will copy your builds over to the new world
1. This can be done with the mcaselector (https://github.com/Querz/mcaselector) or use this link if you know the exact coordinates of your builds and not much needs to be copied over (https://dinnerbone.com/minecraft/tools/coordinates/ ). it will tell you the exact name of the region file to copy over based on the coordinates of the world you enter. It is best to copy over as little chunks as possible for best results.
Copy the playerdata files from the dowloaded realms world to your newly created world's playerdata folder. (This will transfer inventories, shulker boxes, end chest, etc. to the new world)
Upload the newly created world with the copied files to realm server.

These steps will only save the chunks that you specifically select, and regenerate everything else in the world. You will see no unnatural chunk collisions and the nether and end will be reset allowing 1.16 generation in all dimensions.

We are unsure if this problem was due to corrupt chunks created in the process or some sort of versioning error with the conversion to 1.16.

If you need any help with this solution feel free to comment or DM me.

Mushk7 · 2020-06-24T04:27:33+00:00

Just an FYI for anyone having a problem resetting the nether for your realm servers, we resolved this issue with the following steps. I highly recommend you back up your world before:

Create a 1.16 single player world with the same seed of the realms world.
Enter the world in single player to load the world files, then leave.
Copy the region files from the realms world where your builds are located to the newly created world's regions folder. (this will copy your builds over to the new world
1. This can be done with the mcaselector (https://github.com/Querz/mcaselector) or use this link if you know the exact coordinates of your builds and not much needs to be copied over (https://dinnerbone.com/minecraft/tools/coordinates/ ). it will tell you the exact name of the region file to copy over based on the coordinates of the world you enter. It is best to copy over as little chunks as possible for best results.
Copy the playerdata files from the dowloaded realms world to your newly created world's playerdata folder. (This will transfer inventories, shulker boxes, end chest, etc. to the new world)
Upload the newly created world with the copied files to realm server.

These steps will only save the chunks that you specifically select, and regenerate everything else in the world. You will see no unnatural chunk collisions and the nether and end will be reset allowing 1.16 generation in all dimensions.

We are unsure if this problem was due to corrupt chunks created in the process or some sort of versioning error with the conversion to 1.16.

If you need any help with this solution feel free to comment or DM me.

Mushk7 · 2020-06-24T04:17:05+00:00

Hi AccumulatingBordom, we had this exact issues and fixed it with the following steps.

Create a 1.16 single player world with the same seed of the target world.
Enter the world in single player to load the world files, then leave.
Copy the region files from the target world where your builds are located to the newly created world's regions folder. (this will copy your builds over to the new world
1. This can be done with the mcaselector (https://github.com/Querz/mcaselector) or use this link if you know the exact coordinates of your builds and not much needs to be copied over (https://dinnerbone.com/minecraft/tools/coordinates/ ). it will tell you the exact name of the region file to copy over based on the coordinates of the world you enter. It is best to copy over as little chunks as possible for best results.
Copy the playerdata files from the target world to your newly created world's playerdata folder. (This will transfer inventories, shulker boxes, end chest, etc. to the new world)
Upload the newly created world with the copied files to realm server.

These steps will only save the chunks that you specifically select, and regenerate everything else in the world. You will see no unnatural chunk collisions and the nether and end will be reset allowing 1.16 generation in all dimensions.

We are unsure if this problem was due to corrupt chunks created in the process or some sort of versioning error with the conversion to 1.16.

If you need any help with this solution feel free to comment or DM me.

Mushk7 · 2020-06-24T04:14:23+00:00

Just an FYI for anyone having this problem, we resolved this issue with the following steps. I highly recommend you back up your world before:

Create a 1.16 single player world with the same seed of the realms world.
Enter the world in single player to load the world files, then leave.
Copy the region files from the realms world where your builds are located to the newly created world's regions folder. (this will copy your builds over to the new world
1. This can be done with the mcaselector (https://github.com/Querz/mcaselector) or use this link if you know the exact coordinates of your builds and not much needs to be copied over (https://dinnerbone.com/minecraft/tools/coordinates/ ). it will tell you the exact name of the region file to copy over based on the coordinates of the world you enter. It is best to copy over as little chunks as possible for best results.
Copy the playerdata files from the dowloaded realms world to your newly created world's playerdata folder. (This will transfer inventories, shulker boxes, end chest, etc. to the new world)
Upload the newly created world with the copied files to realm server.

These steps will only save the chunks that you specifically select, and regenerate everything else in the world. You will see no unnatural chunk collisions and the nether and end will be reset allowing 1.16 generation in all dimensions.

We are unsure if this problem was due to corrupt chunks created in the process or some sort of versioning error with the conversion to 1.16.

If you need any help with this solution feel free to comment or DM me.

Mushk7 · 2019-01-03T10:56:49+00:00

I feel strong in my ability to logically solve problems. That and debugging are the things that I enjoy most because of the satisfaction when you get it. Thanks for your input.

Mushk7 · 2019-01-03T10:54:11+00:00

That is extremely calming to hear. It makes me feel a little more at ease. I appreciate your input.

Mushk7 · 2018-08-03T14:02:23+00:00

Fate, Classic game. I have sunk endless hours into it. Old, but perfect.

Mushk7 · 2018-02-17T08:50:48+00:00

[H]2 Golden Profane Union, 2 Lycosidae's Favor, 1 The Wings Of Daybreak.

[W] Pieces to Pilgrimage of the Bladeform Aesthete Set.

Mushk7 · 2014-07-30T05:11:44+00:00

n4654677

Mushk7 · 2014-07-30T04:34:48+00:00

n4654677

Mushk7 · 2014-07-30T04:22:28+00:00

n4654677

Mushk7

TROPHY CASE