Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

galvia

Testers
  • Content Count

    75
  • Joined

  • Last visited


Reputation Activity

  1. Like
    galvia got a reaction from Raindog in 5.92.0 Feedback Reports for 6/6/2019   
    Hey folks and @vkromas @jtoddcoleman, have a bit of feedback for you around sieging in 5.9x from the perspective of a smaller guild but a very active one. Currently sieging is extremely defenders oriented for a couple key reasons, and it is making sieging without an overwhelming force pretty arduous. There are two primary contributing factors to this problem:

    First, balistas need to be looked at. Currently the fire AOE they shoot out creates no visible ground AoE but ticks for thousands of damage. If you do not instantly react to your health going down during the fight you will likely die without healer intervention, and even with healer intervention if you don't instantly run out of it you're in big trouble. You can check this out in action in YUMX's Slaughter of Kurro WarStory, I've linked directly to the part of the video that demonstrates this. There is a red circle AOE for the attacker, but nothing for the defender, and you can watch many players die to this bug.

    The Fire AOE is a unique and great mechanic for it's purpose, but it also is being used for what I think are unintended purposes that really stall out sieges. Which brings me to my next point of feedback on balistas - they should not be able to fire into your own keep. Currently the prevailing strategy on defense is to have a group of stealthers on defence spread out around the keep walls after the wall has been breached, holding onto MKIV balistas and waiting for the attackers to commit to an entry path to the tree of life. These evasive characters will place balista along the walls as the defenders push in, or when they have sight on them, and dump fire AOEs and healing boxes onto the clashing forces. This destroys the offence unless they can crush these players spread out across the entire keep before burning to death, and it strongly benefits the defending team to fight under the cover of balista fire into their own keep (standing in healing and damage circles is currently the strongest way to survive and fight). You can secure a single area of the keep but it's a losing battle to the combined might of the fire AOE and the defensive forces positioned favourably already. If balistas can only fire outward (as they do in real life) this would save a lot of balista headaches.

    The second thing, which is less oppressive but still bad, is the defenders rez advantage on defence. I believe that the defenders should have an advantage around resurrecting during a siege, but currently it is way too forgiving for the defenders. As it stands right now, even if you breach at the dragon statue, the defence has MANY opportunities to continuously reinforce their line after dying while the offence often has 5+ minute run backs after dying if a res is not possible (which it often isn't, due to the number of archers and the fact that the defenders can still fight you). The typical flow for our successful breaches looks a bit like this.
    Breach the wall after defending our siege equipment. Hope that the defence loses players to start up the longer respawn timers. Enter the keep and begin clearing out balistas that are being spammed while being poked at by the defence. This gives them time to setup blight bomb traps, spread people out around the walls. Hope we haven't lost too many people to bugged fire AOE or the defenders. Once we feel relatively safe on a particular entry vector, rush in with our whole force and hope we can win the tree of life fight. This means committing forces that can no longer clear out balistas, placing our own that aren't being threatened by archer fire, and hoping we can catch the defence in our own firebox from the 1 - 2 balistas we have space to put down. There are tons of counter play to this strategy by the defence, outside of the archer advantage and their ability to fight us in the first place in an even matchup between the two forces. We attempt to win the fight on the tree of life through fire AOEs and the defenders abilities and the archers. Killing a tree of life takes time with pesky defenders healing it and killing us. If we kill defenders, they rez and are back in the fight in a minute without death shroud and right beside their allies. If we die, that player is likely out for the rest of that push. If we start to lose the fight, we need to immediately back up to the bane tree. Retreating is a good way to lose straggling players in the keep. On a lost push we often don't have enough time to try again before our respawns make it back to the fight, and we are forced to fight on the banetree with a reduced force. Our time becomes a lot more precious when only a single bane tree spawns as well which is a common bug. On the banetree fight. If we kill their players, they respawn very quickly and can reinforce the fight - we usually kill 1 - 2 players every 30~ seconds against an organized force which means a minute respawn timer isn't always enough to actually gain a numbers advantage and meaningfully push them back. This gets worse as we lose players, because they are 5+ minutes out from reinforcing us, whereas the defenders are back in the fight within 1 - 2 minutes. The assaults we've won this campaign are a result of one of two things:
    An overwhelming force. We crush the defence with numbers and gear and they can't react in time before we take the tree. A huge tactical error on the part of the defenders. Wiping them out on the bane tree very quickly, they all die to a firebox, they don't realize they can spam balistas, etc. I'd suggest either increasing the respawn timer on fly back for rezzing, increase it when as siege is active, or make it ramp up faster in severity while siege is active. There are a ton of ways to fix these gameplay problems, but overall this is much better than the previous death shroud mechanics that could be easily circumvented.
     
    TL;DR
    Balista fireboxes need to show a ground AOE for the enemy + an animation for the shot. Balistas should only be able to fire out of the keep or on a sharper angle, so that you can't fire into your own keep. Balistas shouldn't be able to be placed by the attacking force on a defenders keep. Defenders have too significant a res advantage and stalling advantage against attackers. I love you longtime.  
  2. Like
    galvia reacted to Hungry in 5.92.0 Feedback Reports for 6/6/2019   
    There is always more work to be done. They still need to provide avenues of progression that players with few friends and less gear to level more efficiently than they do now. They are adding gear drops to wartribes, caravans, fixing XP awards from kills, and XP for all activities at some point we just need it sooner rather than later.  I have a guild I run that supports each other and we are all farming these mobs for discs anyway, so these targeted farming methods is how we level since it is so much more efficient for us than solo avenues we would never bother doing anything else.  Some random Order player that is playing the game with no guild is stuck getting 50 XP a mob and using bandages every 3 pulls. I've been there, it sucks butt.  With my initial post I wasn't trying to say that leveling was fixed for everyone, just I was one of the nerds who farmed wartribes and ancients every respawn timer when 5.9 came out (when people were still playing the game) and the buff to their drops makes me much happier.
    I think I'm in the minority when I say people on the forums overblow the grind. My green cleric alt was made by a white vessel necro pre-goggles and using white gear with no jewelry until about a week ago and I performed just fine in PVP. Most of my guild was in white armor and all but a few select DPS players with white weapons (DPS got blue runic) and blue jewelry. Weapons and jewelry are the least resource intensive stuff to make.
    We are all in blues everything now but it's been how long since the wipe? And most of us only play 3-4 hours a night. I think they still need to add systems to lower the grind but I don't think it is as egregious as most people say. Either that, or we have different expectations about how a sandbox PVP MMO works.
    The reason we need a grind loop, in my opinion, is because the difference between a sandbox MMO and a MOBA or something is how we vie for wealth, resources, and power. If none of those things are at stake we are simply fighting for the sake of competition. Which can be fine, but Crowfall will never be as purely competitive as something like Dota or Quake so why bother trying to bring that same experience.  I don't see value in Crowfall being a persistent MOBA.
     
    From the EVE players I know that operate in nullsec they say the thing that makes the game exciting are the things they have to lose if they don't perform. Territory, money, items, prestige. That is how I felt playing Shadowbane as well.  From what I understand that IS the point of this kind of MMO.  The problem is right now there aren't enough people playing for pretty much ANY PVP to happen between all the PVE, and spirit banks along with no true ownership of holdings makes it so the only thing that is ever at stake is who wins the campaign.
  3. Like
    galvia reacted to Hungry in 5.92.0 Feedback Reports for 6/6/2019   
    (Disciplines, crafting resources, and accessories not pictured)
     
    This was acquired in a single hour of work by 2 people.  Thank you for making the wartribe drops more generous as it really helps reduce the grind.
  4. Like
    galvia reacted to Duffy in 5.92.0 Feedback Reports for 6/6/2019   
    Siege equipment in general needs a look at, right now using ballistas to actually counter catapults and players is mostly a waste of resources unless the attackers don’t realize how easily a few ranged players or a single catapult shot can destroy them. 
    This helps reinforce the desire to utilize them (and they are too effective here) to defend the tree room or internal areas, albeit they are still easy to destroy if someone can get into the position to do so.
    I think maybe they were originally too balanced around folks utilizing Siege Engineer, but no one wants to run it now that theirs a longer term cost to doing so. We only sometimes have new folks on common vessels running it.
    Trebs have fallen out completely, tho they have the problem of entirely negating any defense besides sallying out, which requires a strong advantage anyways - which means no reason to fight inside the walls.
    As for respawning, I’m not sure yet, it’s definitely a lot better than it used to be. But I’m not convinced defender respawn is problematic yet. I also somewhat feel like the intention of a siege is that you should be bringing some larger numbers to overcome the inherent advantages, otherwise you shouldn’t be sieging. I’m not sure, need to dwell on it more and maybe experience it more from the attackers viewpoint.
  5. Like
    galvia got a reaction from coffee4ever in 5.92.0 Feedback Reports for 6/6/2019   
    Hey folks and @vkromas @jtoddcoleman, have a bit of feedback for you around sieging in 5.9x from the perspective of a smaller guild but a very active one. Currently sieging is extremely defenders oriented for a couple key reasons, and it is making sieging without an overwhelming force pretty arduous. There are two primary contributing factors to this problem:

    First, balistas need to be looked at. Currently the fire AOE they shoot out creates no visible ground AoE but ticks for thousands of damage. If you do not instantly react to your health going down during the fight you will likely die without healer intervention, and even with healer intervention if you don't instantly run out of it you're in big trouble. You can check this out in action in YUMX's Slaughter of Kurro WarStory, I've linked directly to the part of the video that demonstrates this. There is a red circle AOE for the attacker, but nothing for the defender, and you can watch many players die to this bug.

    The Fire AOE is a unique and great mechanic for it's purpose, but it also is being used for what I think are unintended purposes that really stall out sieges. Which brings me to my next point of feedback on balistas - they should not be able to fire into your own keep. Currently the prevailing strategy on defense is to have a group of stealthers on defence spread out around the keep walls after the wall has been breached, holding onto MKIV balistas and waiting for the attackers to commit to an entry path to the tree of life. These evasive characters will place balista along the walls as the defenders push in, or when they have sight on them, and dump fire AOEs and healing boxes onto the clashing forces. This destroys the offence unless they can crush these players spread out across the entire keep before burning to death, and it strongly benefits the defending team to fight under the cover of balista fire into their own keep (standing in healing and damage circles is currently the strongest way to survive and fight). You can secure a single area of the keep but it's a losing battle to the combined might of the fire AOE and the defensive forces positioned favourably already. If balistas can only fire outward (as they do in real life) this would save a lot of balista headaches.

    The second thing, which is less oppressive but still bad, is the defenders rez advantage on defence. I believe that the defenders should have an advantage around resurrecting during a siege, but currently it is way too forgiving for the defenders. As it stands right now, even if you breach at the dragon statue, the defence has MANY opportunities to continuously reinforce their line after dying while the offence often has 5+ minute run backs after dying if a res is not possible (which it often isn't, due to the number of archers and the fact that the defenders can still fight you). The typical flow for our successful breaches looks a bit like this.
    Breach the wall after defending our siege equipment. Hope that the defence loses players to start up the longer respawn timers. Enter the keep and begin clearing out balistas that are being spammed while being poked at by the defence. This gives them time to setup blight bomb traps, spread people out around the walls. Hope we haven't lost too many people to bugged fire AOE or the defenders. Once we feel relatively safe on a particular entry vector, rush in with our whole force and hope we can win the tree of life fight. This means committing forces that can no longer clear out balistas, placing our own that aren't being threatened by archer fire, and hoping we can catch the defence in our own firebox from the 1 - 2 balistas we have space to put down. There are tons of counter play to this strategy by the defence, outside of the archer advantage and their ability to fight us in the first place in an even matchup between the two forces. We attempt to win the fight on the tree of life through fire AOEs and the defenders abilities and the archers. Killing a tree of life takes time with pesky defenders healing it and killing us. If we kill defenders, they rez and are back in the fight in a minute without death shroud and right beside their allies. If we die, that player is likely out for the rest of that push. If we start to lose the fight, we need to immediately back up to the bane tree. Retreating is a good way to lose straggling players in the keep. On a lost push we often don't have enough time to try again before our respawns make it back to the fight, and we are forced to fight on the banetree with a reduced force. Our time becomes a lot more precious when only a single bane tree spawns as well which is a common bug. On the banetree fight. If we kill their players, they respawn very quickly and can reinforce the fight - we usually kill 1 - 2 players every 30~ seconds against an organized force which means a minute respawn timer isn't always enough to actually gain a numbers advantage and meaningfully push them back. This gets worse as we lose players, because they are 5+ minutes out from reinforcing us, whereas the defenders are back in the fight within 1 - 2 minutes. The assaults we've won this campaign are a result of one of two things:
    An overwhelming force. We crush the defence with numbers and gear and they can't react in time before we take the tree. A huge tactical error on the part of the defenders. Wiping them out on the bane tree very quickly, they all die to a firebox, they don't realize they can spam balistas, etc. I'd suggest either increasing the respawn timer on fly back for rezzing, increase it when as siege is active, or make it ramp up faster in severity while siege is active. There are a ton of ways to fix these gameplay problems, but overall this is much better than the previous death shroud mechanics that could be easily circumvented.
     
    TL;DR
    Balista fireboxes need to show a ground AOE for the enemy + an animation for the shot. Balistas should only be able to fire out of the keep or on a sharper angle, so that you can't fire into your own keep. Balistas shouldn't be able to be placed by the attacking force on a defenders keep. Defenders have too significant a res advantage and stalling advantage against attackers. I love you longtime.  
  6. Like
    galvia got a reaction from Hungry in 5.92.0 Feedback Reports for 6/6/2019   
    Hey folks and @vkromas @jtoddcoleman, have a bit of feedback for you around sieging in 5.9x from the perspective of a smaller guild but a very active one. Currently sieging is extremely defenders oriented for a couple key reasons, and it is making sieging without an overwhelming force pretty arduous. There are two primary contributing factors to this problem:

    First, balistas need to be looked at. Currently the fire AOE they shoot out creates no visible ground AoE but ticks for thousands of damage. If you do not instantly react to your health going down during the fight you will likely die without healer intervention, and even with healer intervention if you don't instantly run out of it you're in big trouble. You can check this out in action in YUMX's Slaughter of Kurro WarStory, I've linked directly to the part of the video that demonstrates this. There is a red circle AOE for the attacker, but nothing for the defender, and you can watch many players die to this bug.

    The Fire AOE is a unique and great mechanic for it's purpose, but it also is being used for what I think are unintended purposes that really stall out sieges. Which brings me to my next point of feedback on balistas - they should not be able to fire into your own keep. Currently the prevailing strategy on defense is to have a group of stealthers on defence spread out around the keep walls after the wall has been breached, holding onto MKIV balistas and waiting for the attackers to commit to an entry path to the tree of life. These evasive characters will place balista along the walls as the defenders push in, or when they have sight on them, and dump fire AOEs and healing boxes onto the clashing forces. This destroys the offence unless they can crush these players spread out across the entire keep before burning to death, and it strongly benefits the defending team to fight under the cover of balista fire into their own keep (standing in healing and damage circles is currently the strongest way to survive and fight). You can secure a single area of the keep but it's a losing battle to the combined might of the fire AOE and the defensive forces positioned favourably already. If balistas can only fire outward (as they do in real life) this would save a lot of balista headaches.

    The second thing, which is less oppressive but still bad, is the defenders rez advantage on defence. I believe that the defenders should have an advantage around resurrecting during a siege, but currently it is way too forgiving for the defenders. As it stands right now, even if you breach at the dragon statue, the defence has MANY opportunities to continuously reinforce their line after dying while the offence often has 5+ minute run backs after dying if a res is not possible (which it often isn't, due to the number of archers and the fact that the defenders can still fight you). The typical flow for our successful breaches looks a bit like this.
    Breach the wall after defending our siege equipment. Hope that the defence loses players to start up the longer respawn timers. Enter the keep and begin clearing out balistas that are being spammed while being poked at by the defence. This gives them time to setup blight bomb traps, spread people out around the walls. Hope we haven't lost too many people to bugged fire AOE or the defenders. Once we feel relatively safe on a particular entry vector, rush in with our whole force and hope we can win the tree of life fight. This means committing forces that can no longer clear out balistas, placing our own that aren't being threatened by archer fire, and hoping we can catch the defence in our own firebox from the 1 - 2 balistas we have space to put down. There are tons of counter play to this strategy by the defence, outside of the archer advantage and their ability to fight us in the first place in an even matchup between the two forces. We attempt to win the fight on the tree of life through fire AOEs and the defenders abilities and the archers. Killing a tree of life takes time with pesky defenders healing it and killing us. If we kill defenders, they rez and are back in the fight in a minute without death shroud and right beside their allies. If we die, that player is likely out for the rest of that push. If we start to lose the fight, we need to immediately back up to the bane tree. Retreating is a good way to lose straggling players in the keep. On a lost push we often don't have enough time to try again before our respawns make it back to the fight, and we are forced to fight on the banetree with a reduced force. Our time becomes a lot more precious when only a single bane tree spawns as well which is a common bug. On the banetree fight. If we kill their players, they respawn very quickly and can reinforce the fight - we usually kill 1 - 2 players every 30~ seconds against an organized force which means a minute respawn timer isn't always enough to actually gain a numbers advantage and meaningfully push them back. This gets worse as we lose players, because they are 5+ minutes out from reinforcing us, whereas the defenders are back in the fight within 1 - 2 minutes. The assaults we've won this campaign are a result of one of two things:
    An overwhelming force. We crush the defence with numbers and gear and they can't react in time before we take the tree. A huge tactical error on the part of the defenders. Wiping them out on the bane tree very quickly, they all die to a firebox, they don't realize they can spam balistas, etc. I'd suggest either increasing the respawn timer on fly back for rezzing, increase it when as siege is active, or make it ramp up faster in severity while siege is active. There are a ton of ways to fix these gameplay problems, but overall this is much better than the previous death shroud mechanics that could be easily circumvented.
     
    TL;DR
    Balista fireboxes need to show a ground AOE for the enemy + an animation for the shot. Balistas should only be able to fire out of the keep or on a sharper angle, so that you can't fire into your own keep. Balistas shouldn't be able to be placed by the attacking force on a defenders keep. Defenders have too significant a res advantage and stalling advantage against attackers. I love you longtime.  
  7. Like
    galvia got a reaction from JamesGoblin in 5.92.1 LIVE Bug Reports for 6/13/2019   
    Fell through the world in the area of 3901 3111 in Rae. There seems to be a wide area there that you can just fall into.
  8. Like
    galvia reacted to Pann in War Story of the Week: Galvia   
    Congratulations to Galvia whose video has been selected as our Crowfall® War Story of the Week!

    FULL STORY
    (Note: We're switching these announcements from Fridays to Wednesdays.) 
  9. Thanks
    galvia reacted to jtoddcoleman in my frustration with crowdfunding, explained   
    Hey folks, just a quick note, apparently some people took my statement on yesterday’s livestream that “I will never do crowdfunding again” as frustration with community feedback.  Nothing could be further from the truth; this game wouldn’t be here without you and frankly won’t be successful without you.  
    That said, I was being earnest about my feelings on crowdfunding; I think it’s a particularly challenging way to develop a game for a few reasons:
    1. You have to build excitement/hype at the beginning of the project, and it’s impossible to keep that excitement up for the duration of the project.  That means your fighting an uphill battle of fatigue in the press and the audience going into launch.  Not good.
    2. Supporting a “live” service for the duration of development, with the accompanying build process, deployment pipeline and operational environment is very expensive and time consuming.
    3. The process exposes all of our missteps to the world, and that sucks.  No one would prefer to make their mistakes in front of a live studio audience.
    4. The nature of the beast is that you're putting undercooked systems and unbalanced tables in front of players.  As you know, this can often lead to experiences that are not fun. Managing expectations and keeping players happy is especially difficult under these conditions.
    All of that said, I apologize if it came across in any way as a swipe at you guys.  It absolutely wasn’t intended that way.  It can be hard to get feedback some times, but I want to make this game great for you and I fully recognize that we can’t do it without you.
    Next time, I’ll go get the funding lined up first and ask you for your feedback —without also asking for your money.  That’s all.
    Thanks,
    Todd
  10. Thanks
    galvia got a reaction from JamesGoblin in Warstory - Day 1 Destruction   
    The Trial of Maeve started with a bang! Here's a video showcasing a bunch of fights I got into in the first hour of the campaign.
  11. Thanks
    galvia got a reaction from Groovin in Warstory - Day 1 Destruction   
    The Trial of Maeve started with a bang! Here's a video showcasing a bunch of fights I got into in the first hour of the campaign.
  12. Like
    galvia got a reaction from JamesGoblin in 5.90 LIVE Bug Reports for 5/17/2019   
    Illusionist makes you T-pose now.

  13. Like
    galvia got a reaction from JamesGoblin in 5.90 LIVE Bug Reports for 5/17/2019   
    Brigand traps can be placed multiple times and are triggering multiple times on individual targets currently.

    Good buff for the most nerfed class in 5.8, probably not intended gameplay.
  14. Thanks
    galvia got a reaction from JamesGoblin in 5.90 LIVE Bug Reports for 5/17/2019   
    Looks like Balista AoE is ticking extremely high and the ground AoE is not appearing currently. Had a number of players die very quickly to a single balista shot in the Tree of Life room tonight without any indicator that they were in a danger zone.

    Two points of feedback on that:
    1. Please make the AoE show up again, and maybe add a sound effect.
    2. I'm unsure if it is intended to be able to fire on your own tree in the first place.
  15. Sad
    galvia got a reaction from Raindog in 5.90 LIVE Bug Reports for 5/17/2019   
    Using materials for a Runic Great Mace Head resulted in a normal Mace Head:


     
    No mistakes made in the crafting stages, and there is no other way of getting FDM on this component. It will also not slot into the runic mace because of this problem.
  16. Like
    galvia got a reaction from JamesGoblin in 5.90 LIVE Bug Reports for 5/17/2019   
    Using materials for a Runic Great Mace Head resulted in a normal Mace Head:


     
    No mistakes made in the crafting stages, and there is no other way of getting FDM on this component. It will also not slot into the runic mace because of this problem.
  17. Like
    galvia reacted to Hungry in 5.90 LIVE Bug Reports for 5/17/2019   
    We rezzed someone who had been dead for a few minutes and his animations broke.  It was quite hilarious.
    https://gfycat.com/FoolhardyClearcutFrilledlizard
    https://gfycat.com/AfraidFaithfulBarb
     
     
  18. Like
    galvia got a reaction from JamesGoblin in 5.90 LIVE Bug Reports for 5/17/2019   
    Tested twice to make sure I am not crazy and confirmed that this pattern is broken.
  19. Haha
    galvia got a reaction from Tyrannicall in #Warstories: Gerbilled, Rolled-up and Put Down   
  20. Haha
    galvia got a reaction from Mag_Nifico in #Warstories: Gerbilled, Rolled-up and Put Down   
  21. Thanks
    galvia got a reaction from mandalore in #Warstories: Gerbilled, Rolled-up and Put Down   
  22. Haha
    galvia got a reaction from Ble in #Warstories: Gerbilled, Rolled-up and Put Down   
  23. Like
    galvia got a reaction from soulein in #Warstories: Gerbilled, Rolled-up and Put Down   
  24. Sad
    galvia got a reaction from BenQ in #Warstories: Gerbilled, Rolled-up and Put Down   
  25. Thanks
    galvia reacted to Phr00t in 30 minutes in the life of a fully trained Skinner   
    So let's say you have a guild member who asks you for some blue or epic flexible hide? What do you do? You go farm rank 9s!

    How long will you need to farm to acquire enough blue, or even epic quality materials to make a full set of armor? Well, just watch the video and do the math..
    Spoiler: Much longer than a miner.
    TLDW: stats and results at the end of the video.
     
     
     
×
×
  • Create New...