Fullhouse Posted May 11, 2011 Share Posted May 11, 2011 How do you keep a working from becoming over too quickly? Or better yet a worker you dont want to move up the card. I have some workers who have started to become uphappy because of their current push. I checked with the booking team and true enough it will say this particular worker Ideally would be used as a upper midcarder based on his popularity and the rest of the roster. However, my upper midcard is getting too crowded so I dont want to add any more at this time. Is there anything I can do to hold these workers back so to speak so they are ideally to be used in the midcard or their current push? Link to comment Share on other sites More sharing options...
luminafire Posted May 14, 2011 Share Posted May 14, 2011 <p>Give them some losses. Chances are if they're that over they have momentum that might be helpful for getting over the guys you want pushed. The drawback is that they might become unhappy with the amount of losses they've taken (and when you give them wins again, they might go back to being too over).</p><p> </p><p> Of course, you should always compare the current stars to the ones that are accidentally getting over. You might have guys that'll do better in that spot.</p><p> </p><p> OR you could try to sign guys that are more popular than the guys you don't want pushed yet to drive a wedge in between them and your main guys.</p><p> </p><p> Giving them losses is probably the most practical thing to do. I know how that is-- I have a roster full of A and A* popularity guys but for some reason this generated wrestler named Melvin Freebush keeps getting a main event auto-push and he complains if he's an upper midcarder. He's not that good in the ring and his popularity cap is B+ and yet he still is getting pushed more than other more-talented and more-popular guys I have on the roster. It had me so annoyed at some point, I wanted to fire him lol.</p> Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.