Guild Wars Forums - GW Guru
 
 

Go Back   Guild Wars Forums - GW Guru > The Hall of Knowledge > The Campfire

Notices

Reply
 
Thread Tools Display Modes
Old Dec 11, 2006, 02:54 AM // 02:54   #41
Just Plain Fluffy
 
Ensign's Avatar
 
Join Date: Dec 2004
Location: Berkeley, CA
Guild: Idiot Savants
Advertisement

Disable Ads
Default

Short version:

If you're using Mark of Rodgort as a 'put this hex on a lot of dudes because my team has a lot of undirected fire damage and getting burning out of it would be awesome' hex, then it would be good.

If you're using Mark of Rodgort as a 'I'm going to put Mark of Rodgort on this guy, and then I'm going to deal fire damage to him to set him on fire too!', then the skill is complete shit. Thanks for playing.

Peace,
-CxE
__________________
Don't argue with idiots. They bring you to their level and beat you with experience.
Ensign is offline   Reply With Quote
Old Dec 11, 2006, 03:10 AM // 03:10   #42
Grindin'
 
Thom Bangalter's Avatar
 
Join Date: Dec 2005
Location: MO
Profession: E/Mo
Default

Thanks for the cliff's notes ensign
Thom Bangalter is offline   Reply With Quote
Old Dec 11, 2006, 04:15 AM // 04:15   #43
Wilds Pathfinder
 
Join Date: Aug 2005
Default

Quote:
Originally Posted by Ensign
If you're using Mark of Rodgort as a 'I'm going to put Mark of Rodgort on this guy, and then I'm going to deal fire damage to him to set him on fire too!', then the skill is complete shit. Thanks for playing.
The only exception to that IMO is a PvE Barrage Ranger. The AoE's of Barrage and MoR match up, it's spammable, and energy is no longer a huge problem with the reduction in MoR's energy cost and the huge buff to Glyph of Lesser Energy.
Grammar is offline   Reply With Quote
Old Dec 11, 2006, 07:20 AM // 07:20   #44
Grindin'
 
Thom Bangalter's Avatar
 
Join Date: Dec 2005
Location: MO
Profession: E/Mo
Default

That falls under the 'undirected fire damage' part.
Thom Bangalter is offline   Reply With Quote
Old Dec 11, 2006, 10:37 AM // 10:37   #45
Jungle Guide
 
Join Date: Aug 2005
Default

Quote:
The only exception to that IMO is a PvE Barrage Ranger. The AoE's of Barrage and MoR match up, it's spammable, and energy is no longer a huge problem with the reduction in MoR's energy cost and the huge buff to Glyph of Lesser Energy.
It doesn't matter whether the AoEs match up. If barrage had a "nearby" AoE would that make MoR worse?

IMO it doesn't matter where the burning trigger comes from-if you can keep all the hexed foes constantly burning with MoR then it has done its job, this distinction between fire damage coming from teammates and fire damage coming from you seems rather arbitrary.
Symbol is offline   Reply With Quote
Old Dec 11, 2006, 02:08 PM // 14:08   #46
Academy Page
 
jacen110091's Avatar
 
Join Date: Oct 2006
Guild: The Eightfold Way [TEW]
Profession: E/Mo
Default

Quote:
Originally Posted by Ensign
Short version:

If you're using Mark of Rodgort as a 'put this hex on a lot of dudes because my team has a lot of undirected fire damage and getting burning out of it would be awesome' hex, then it would be good.

If you're using Mark of Rodgort as a 'I'm going to put Mark of Rodgort on this guy, and then I'm going to deal fire damage to him to set him on fire too!', then the skill is complete shit. Thanks for playing.

Peace,
-CxE
LMAO

heh, sounds fair mate!
although I'd again mention that MoR is a very good skill for buggers like me who are "Prophecies Only"
jacen110091 is offline   Reply With Quote
Reply

Share This Forum!  
 
 
           

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 04:49 AM // 04:49.


Powered by: vBulletin
Copyright ©2000 - 2016, Jelsoft Enterprises Ltd.
jQuery(document).ready(checkAds()); function checkAds(){if (document.getElementById('adsense')!=undefined){document.write("_gaq.push(['_trackEvent', 'Adblock', 'Unblocked', 'false',,true]);");}else{document.write("