1 |
@Shaman why am I being punished for someone else going AFK?
|
1 |
@Shaman why am I being punished for someone else going AFK?
|
2 |
\n
|
2 |
\n
|
3 |
Fact is that the reason for going AFK is irrelevant to the outcome, be it a crash or malice. Result is the same and the result is what I want to change, I am given no warning that I am about to lose control of units I'm controlling. I don't care how punished the AFK people are.
|
3 |
Fact is that the reason for going AFK is irrelevant to the outcome, be it a crash or malice. Result is the same and the result is what I want to change, I am given no warning that I am about to lose control of units I'm controlling. I don't care how punished the AFK people are.
|
4 |
\n
|
4 |
\n
|
5 |
It's also extremely dishonest to even argue about "crashes" as those are so extremely rare, even if they do happen then players stand practically no chance of reconnecting into a longer game as their hardware will never permit them to catch up.
|
5 |
It's also extremely dishonest to even argue about "crashes" as those are so extremely rare, even if they do happen then players stand practically no chance of reconnecting into a longer game as their hardware will never permit them to catch up.
|
6 |
\n
|
6 |
\n
|
7 |
I'm 99.9% of the time the highest ranking player in a team game, I don't even remember the last time I didn't receive someone elses base in a game. If this is not addressed then I will start gifting these units to random people on the team, most likely the lowest ranked ones, until people that lack empathy can understand how annoying this is. Perhaps this can be even automated.
|
7 |
I'm 99.9% of the time the highest ranking player in a team game, I don't even remember the last time I didn't receive someone elses base in a game. If this is not addressed then I will start gifting these units to random people on the team, most likely the lowest ranked ones, until people that lack empathy can understand how annoying this is. Perhaps this can be even automated.
|
8 |
\n
|
8 |
\n
|
9 |
There's little more tilting than having an AFKer/leaver and being simultaneously spammed with unit shared messages/beeping, while not even being able to retain control or do anything about it. Allow me to opt out, mitigate the penalty for me or I will opt out in my own way.
|
9 |
There's little more tilting than having an AFKer/leaver and being simultaneously spammed with unit shared messages/beeping, while not even being able to retain control or do anything about it. Allow me to opt out, mitigate the penalty for me or I will opt out in my own way.
|
|
|
10 |
\n
|
|
|
11 |
Perhaps something like this?
|
|
|
12 |
{{{local function GiveUnit(unitID,newTeamID)
|
|
|
13 |
local oldSelectedUnits = Spring.GetSelectedUnits()
|
|
|
14 |
Spring.SelectUnitArray({unitID})
|
|
|
15 |
Spring.ShareResources(newTeamID,"units")
|
|
|
16 |
Spring.SelectUnitArray(oldSelectedUnits)
|
|
|
17 |
end
|
|
|
18 |
\n
|
|
|
19 |
function widget:UnitGiven(unitID, unitDefID, unitTeamID, oldTeamID)
|
|
|
20 |
if Spring.ValidUnitID(unitID) and unitTeamID == Spring.GetMyTeamID() then
|
|
|
21 |
if Spring.AreTeamsAllied(unitTeamID, oldTeamID) then
|
|
|
22 |
GiveUnit(unitID,oldTeamID)
|
|
|
23 |
end
|
|
|
24 |
end
|
|
|
25 |
end}}}
|