RAF & battle.net warning (30 day waiting period)

So I got my new RAF'ed team to 60.99 ($5 vanilla wow during post thanksgiving sale + 10 day trial of BC to get the 0.99 (grant from 59.99 to 60.99)) so I was ready to transfer back the toons to my regular accounts... and got this:

"This character cannot transfer to other Battle.net accounts until a 30-day waiting period has elapsed. You will be eligible to make this transfer on 12/27/2009"

Which sucks... (I had to setup a new battle.net for raf as max is 8 ) as I'm now stuck at 60.9 for another several weeks

So RAF and new accounts if you plan on transferring back is an issue...

Bleh.

Did not really think about that, but yeah they did mention the 30 day thing.

When an account is merged into a B.Net account, transfers to or from the account are locked out for 30 days.

At least you don't need to be part of the same B.Net account to boost with.
You could refer from your keeper/existing B.Net account.
To accounts on your disposable RAF accounts.

I assume this is because their system counts the merger as a transfer. Albeit one where they don't charge you some retarded rate for a simple automated database transaction. It's computationally less intensive than a fricking Google search, except they'll charge you $30 for it.

I called and they waived this cooloff period for me. I didn't realize the 8 account issue when I did my last RAF.

I would call them to try and fix it.

Oh thanks HPAVC - I'll try calling (though with patch and all I hope I won't stay on hold for hours)

Ps: I didn't merge or transfer on the new accounts ; they were freshly created on a fresh battle.net - yet they got that 30 days restriction (and yes my booster is one of my original accounts - I managed to get the 5th to 60 by getting a small group to level 4 and then
E -> 30 + 4 -> D 34/2=17+ 4 + 30 = 51 -> C 51/2 + 4 + 30 = 59 -> B 60 -> A = > 60 giftable levels
)

I will be having the same situation soon. My B.net is full, even though 3 acconuts are inactive. So any RAF will be on a new B.net. The problem you are talking about is getting toons to 60 then moving to old 5 accounts which will have Wrath and your main on them. Since RAF is 90 days, I don't see a problem with the 30 day cooldown, even though I do not think they had our case in mind. More about bot leveling and such. But I am seldom right, due to lack of sleep :o U WoW or you sleep. Easy one!

hmm which phone number to call ? (for the US - looking online I could only find a "webform" (which I filled but I'd like something faster))


ps: the reason why 30 days bug me is that I don't want to create more toons on the throw away accounts; I want to play my new team past 60.9 after transfer to my wotlk accounts (given each toon will cost me $25... I don't want to keep churning new teams on the raf accounts) - I wonder if it's blizz' way to try to get me to upgrade the throwaway to full BC (as that would keep me busy; getting to 70 for a few more days/weeks)

not sure?
Blizzard: Unfortunately, there is currently no phone support feature for the Account Administration team.

I called billing and the guy I talked to said there is nothing he can do about it (after putting me on hold after I insisted) - he said it's for my own security blah blah - so I repeated the point that while I understand that newly merged battle net accounts shouldn't transfer out - my case is different as its a fresh new set of accounts - he said he'll email developers... I did mention someone else said they got that limit lifted but that didn't help.

So looks like I'm blocked until end of december :-( Unless I guess I try again until I get the right person on the phone ? (with patch 3.3 just out the lines are going to be a mess)

Try emailing billing with a thorough explanation and maybe that will be more effective. Hopefully the email will get passed to the correct person to make the decision.

Okay, I hate to sound negative, but from what I've heard, they can't get around the lock out period. The only way I was able to get past this was to have them remove an account from my B.net and then place one of the accounts on the other B.net in it's place. You aren't prevented from transferring within the same B.net account, so this worked for me. The rep told me that the security was set up so that it was impossible for the CSR reps to transfer and that they had to move whole accounts around instead.

Because of this, I'm going to use my $5 accounts as throwaways just for the RaF bonus. Yes it will take me almost twice as long to level up teams, but I won't have to pay $25 for any transfers or upgrade my throwaways. Add in the free 30 days and I don't even have to pay for subs on the main accounts that will get the bonus levels.

- Souca -

Bad news with the AoE change, with my DK booster I really hope my new team that I'm pushing (lvl 15 atm) doesn't get slowed down to badly. Going to double-check if theres any limits to how many targets Pestilence can spread my diseases onto - never noticed any problems with it before, so I hope it's not a new issue......

Edit: the Tooltip for Pestilence says:
"Spreads existing Blood Plague and Frost Fever infections from your target to all other enemies within 10 yards." Good news for anyone boosting with a DK....

cool I was just gonna transfer a bunch of toons off RAF accounts today

GC answered a post about pestilence. It works differently then an actual AOE so it has no cap as to how many mobs it can pass diseases too. The AOE cap shouldn't affect pestilence at all. We "multiboxers" tend to think of it as a nerf due to all the boosting we do, however its actually a boost.

To HPAVC:

Are you sure you were able to get the 30 days lifted ? how exactly ? who did you talk to ?


To Souca:

hmm I have 6 slots in my main battle net (so only 2 free) but only actually use 5 there; so if they could delete 1; move 3 accounts from new->old then I transfer, then delete 1 more and transfer again - that would work - but can they really do that and how long will it take on the phone to get hold of someone able to do that, twice ? maybe december 27 will be there before...