Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
The teleporters can be a bit finicky. Sometimes it seems they won't activate unless you are standing right on them and pointing the cursor right at them in order to get the prompt.
Seems that many of the quests are currently broken. Just had to manually complete "Totally Overpowered," as the Brewery POI failed to load on my Lava Planet.
They'll probably get around to fixing the quests eventually. Hopefully sooner than later as there isn't much to do in game without them once you've fully leveled.
...in which you describe how the quest is literally bugged!
WTF man? Please stop posting this non-solution on all of my posts. I appreciate you're trying to be helpful but dismissing this as not a bug when it is, in fact a bug, isn't helpful at all.
This is great, but I'm not looking for a workaround requiring me to go digging around in game files - as I'm sure the average player also does not want to have to do this - though I'm perfectly capable of doing so, I'd much rather the Devs fix the bug so I don't have to. Instead, you're following me around the threads posting your "This is not a bug!" private multiplayer server workaround when I am playing in offline single-player.
So please stop posting that "this is not a bug" on your workaround, as it might be interpreted by the Devs as fixing the problem, which is does not, and the entire reason for me posting in the first place was so the Devs can be made aware of the problem and fix it. You declaring it fixed with your workaround undermines that. Please stop. The bug needs a permanent fix, not a workaround.
Thanks.
The Devs have no need to fix it, as it has nothing that needs fixing. It is completely in our power as single players or server admins to ensure that the quest can be completed.
Am I playing on one of your multiplayer servers? No, I'm not. So why are you offering a multiplayer private server solution for an offline single-player game? Apples and oranges, dude.
IT IS A BUG! You said yourself that the solar system generation fails 60% of the time to spawn in the type of planet that allows the quest to continue. So it doesn't matter if it's a bug in the quest scripting or rando solar system gen, the fact remains that the game, as currently built, will break this quest 60% of the time. I don't care if you call it a bug, glitch, bad programming or whatever... fact is the quest is BROKEN and needs to be fixed.
As to your solution, you say it yourself that increasing the chance of spawning in the lava world potentially increases the number of lava worlds at system gen. I'm not interesting in having half my solar system populated with lava worlds. I only need the ONE required to complete the quest to spawn, and if you don't mind, I'd sort of like the game to do it all by itself without me having to alter game files and do a workaround. I'm perfectly fine waiting for Devs to fix the problem, provided some know-it-all doesn't c*#k block my threads and declare the problem solved when it isn't. Do you understand that not everybody who plays this game is a server admin, and probably don't want to go needlessly fiddling with system files? We just want the game to work all by itself. If it fails to do so, then by definition, that is a bug preventing the game being played as intended. I'm quite sure the Devs don't expect us to alter game files in order to experience the content of the game.
But, since you have a solution, why are you telling us players and not the Devs. Go talk to them and tell them you have a fix for this broken quest... oh wait, you don't because your fix makes too many lava planets.
I'm happy that you think you're some ultra-skilled game server admin, and glad you've found a workaround for yourself, but you don't get to just decide for the rest of us that your private server fix is some sort of ultimate solution to average single-player gamers, or that it has fixed this obvious problem. The devs have created code that, though faulty solar system generation, has created a state where the required game content needed to complete the quest line has a better than average chance of being absent. THAT is, by definition, a bug, glitch, error, problem... again, I can care less what you call it, but the game is broken and needs a permanent solution. Players should never have to alter game files.
Do you really not see the irony in your beginning a sentence with a "not a bug" declaration while finishing that same sentence by admitting the need to literally employ a workaround?
You have spent more effort in arguing than is needed to adjust your solarsystem in a way to deliver your needs.
Mods and workshop content work properly in-game as intended and do not require users digging around and altering game files. You're just grasping at straws now. Dude, check your ego. Workaround is fine but no, you have NOT solved the problem so please stop trying to double-down on your claim that you have. A workaround IS NOT A PERMANENT SOLUTION and you know this, so just stop. You're welcome to your opinion. What you're NOT welcomed to, is telling the entire community to use your workaround when I am trying to alert Devs to fix their game. You do not have unilateral authority to declare your solution to be THE solution, or to declare my issue solved. You're not Eleon, you're just some know-it-all busybody with a private server acting like you own place.
And again, what you seem to be ignoring is that I fully acknowledge that you have a temporary workaround. Thanks. I appreciate you offering this as what it is, a temporary solution, which I may in fact employ in the mean time. However, the entire point of me posting the problem is for Devs to read in hopes that they eventually address the issue and provide a PERMANENT FIX to the game so we don't have to do any workarounds. Are you really failing to understand that most players don't want to have to do this workaround? Do you not understand that you're actively attempting to prevent the bug being fixed? Seriously... what the actual f$#k is wrong with you? Just go away and mind your own business and play on your private server where you have to alter game files to employ a workaround while simultaneously telling yourself there is no bug. Please, just admit you're wrong and go away and allow me to communicate this issue to the devs. Your interference is not welcome!
You've spent quite a lot of effort yourself trying to prevent Devs from reading my posts. Why? Do you go to auto dealerships and tell people they can fix their poorly designed car at home in their driveway, or do you understand that not everybody is a skilled auto mechanic and just want their car to work when they need it to?
I'd appreciate it if you stop harassing me and attempting to derail my posts. Again, I appreciate the workaround, as I'm sure others do, but I'd like Eleon to provide a permanent solution and I'd like you to stop trying to prevent that from happening.
By declaring that "there is no bug for the Devs to fix," you are literally unilaterally dictating to me that the problem is fixed and insisting that your workaround is THE permanent fix.
Look, you've provided a pretty clear explanation of what is obviously breaking this quest: that the new solar system generation does not ensure the required lava planet spans into the solar system. This is a mistake on Eleons part (I call it a bug but whatever the terminology the quest is prone to being broken by a contradictory game mechanic) and you simply identifying the problem, and finding a temp workaround does not = you permanently solving the problem. The problem persists even in spite of your workaround, which again, I'm probably not interested in using as a permanent solution as in your own admission it can increase the number of lava worlds, thus introducing an imbalance to solar system generation. Again, I'm fine waiting for Eleon to refine RNG for solar systems in a way that guarantees the required content is not subject to randomly being excluded and therefor breaking the quest. They need to fix it so there is 100% chance of that planet being generated because they have made it essential to the quest. If the planet does not spawn, then the quest should not appear in the queue, otherwise it is literally broken content that sends the player on a fruitless chase for a planet that does not exist. Do you really think this is how Eleon intended this game to function? I have no doubt they will fix the quests which are admittedly buggy at the moment and lower on their priority list. We all know this is how EA games do. Let them fix it and in the mean time go ahead and use your "solution," but please stop insisting that the Devs have nothing to fix. When you say that, it's like telling the Devs, "Move along, nothing to see here and this guy AlienPet13 has no bug to report." You do NOT speak for me and my bug is not fixed. It's the way you worded your post in a dismissive, "this is not a bug" way. THAT is you, in fact, trying to prevent the issue being addressed. You don't have a right to hang a "we're closed" sign on my store
What you probably should have done is acknowledge the existence of contradictory game mechanics preventing the needed content being generated and thus, breaking the quest, and offered your workaround as a temp solution until the Devs fix the issue. Instead, you are trying to close the door on the issue by unilaterally declaring it solved with your workaround... which, to be frank, is pretty elitist thing to do since you well know that non-advanced computer users are likely not capable or willing to fiddle around with system files. This is not a solution for those people, which is why I posted the problem for the Devs, not YOU, to read and address.
Again, thanks for the temporary workaround. I't may suffice for advanced users in the mean time. In the long term however, the Devs need to fix this. Please stop telling them otherwise as you do not work for Eleon and are not the authority on weather or not bugs in their game have been fixed.
Seriously dude, if not for your posting your workaround in such an arrogant and dismissive way, or insisting that there is no need for further discussion on the matter, you could have been quite helpful. Thanks for the temp workaround, but if you don't mind, I'd like Eleon to address this, not some game server admin dude who thinks he is the final word on what is and isn't a bug worth looking into by the people who actually develop this game. You do not speak for Eleon and running a couple game servers does not make you a software developer with authority to decide what is important to a company you don't even work for.
It is discussions like this, but much less heated, that will actually lead to the proper action.
And that proper action can only be performed by the Devs, which is the whole point.
Your workaround is quite useful and you've identified the problem perfectly, but again, I posted for the purpose of alerting the Devs to a problem (which quite honestly they probably already know about anyway). And as long as you don't post anything that appears to flag this issue as solved, then the post will hopefully remain to catch the attention of the appropriate people (Eleon developers) if they are in fact, as yet unaware of the issue. This is why we users should probably not go around declaring things solved on their behalf. Let the Devs do their job.
I may try your workaround but like I say, I'd rather not have too many lava planets. At some point I'm sure the Eleon can put in code that guarantees this specific planet type spawns in 100% of games without effecting the diversity of other planet types. Having done a very small bit of coding myself, I know this is pretty easy to do. It's just not very high on their list at the moment as the game has been moved to a whole new version of Unity so there's a lot of stuff that got broken due to the change. They'll get to it, but in the mean time, I think it important that we don't call stuff that we do a fix when only they can provide a permanent solution that does not require anything more from the end user than launching the game and changing in-game settings.
By writing to them personally, as I have done; by writing on their Forum, as I have done, they will discover far more quickly than in the Game's Discussion sections that something is not meeting Player Expectation.
But, to be fair, even if they do listen, it does not mean they will do anything.
Case in point: I wrote in Forum *and* personally emailed one of the Devs about a mistake involving their writing/coding for a Trader. After about 7-10 days, I was written a response and told that "it will be fixed in the next update." Well, it has still not been fixed, and I was "promised" it would have been fixed as long ago as A8.1.
See? Even being directly told by a specific Dev that a very specific situation was indeed taking place, and the actual solution was completely valid...they simply chose not to implement.
Most players know immediately what the Trader issue is, but it is amazingly absent in "bug reports" as well as Feedback.
The only reason I can think of, is the same reason at play here: In both cases, the "problem" can be resolved by the player or admin.
Trust me that I am frustrated with both instances. I simply know the answer/result, and am trying to share it.
And I don't think you have any good reason to assume they do not want to fix broken content in their game. In any case, it's not for you to decide what they will or will not want to fix or to assume for the rest of us that they don't want to hear from users like me, which is why I take issue with you hijacking my comments and declaring the problem solved. You may have solved it for yourself while assuming they will never fix it, or that the problem is too small to be worthy of their attention, but again that's not for you to decide. There are no bugs too small for developers to want to fix as they strive to improve as much as possible in their products and always continue to refine the code and fix bugs even after release. It's just that for now, the quest scripting is low on their priority list as I'm sure they are currently concerned with updating main game features to the new Unity version.
I would assume that when you spoke to a dev who said "we'll fix it in the next update," that may have been before the were aware a new Unity engine was coming out, which I suspect caused them to change their dev plan and update to the new version first. Fixing bugs from previous versions would probably take a back seat to main game functionality... migrating and ensuring functionality of the most major game functions first, as well as their new AI features with base attacks and all, and probably thinking quest scripting can come later as so much of the quest system has been bugged since a8. They know the entire quest system is currently waaaay outdated, so again, I have no reason to believe at some future point we wouldn't likely get an entirely revamped quest system. Right now we have just barely functional quests and a bunch of broken ones (some of the Talon quests are just plain broken too). Anyway, as I recall, there were a lot of plans after A8 that were put on hold when the new Unity came out, probably causing them to prioritize moving to the new engine.
I wonder if maybe the new Unity version coming out may have not been anticipated but hey, a dev has to roll with the punches so they pivoted to concentrate on updating the game engine and integrating the new features first. The new engine may have a better way of implementing quests that may require starting from scratch, which may be why they aren't trying to fix the legacy system and haven't prioritized it just yet. But I'd rather not assume anything and just leave the bug report up just in case they need a reminder for later. And they do in fact pay attention to the forums so I don't consider my bug report a waste of time, nor do other steam users have any right to say so either. It doesn't hurt you to NOT undermine my bug report.
That being said, my issue with you is your policing the steam forums and gate-keeping the importance of this particular bug. Eleon devs can decide that for themselves and even if I'm reporting something they will never address, well, that's literally not for you or anybody other than Eleon to say. So just because you may have a defeatist and cynical view that "the devs don't care about this and will never do anything about it," doesn't mean you have the right to tell me that i can't post about a thing. It's my time to waste and Eleon's place to decide if it merits their attention and, not to put too fine a point on it, it is not for you to interfere with that as to be perfectly honest, it causes you no harm whatsoever to just leave my post alone, since you seem to believe nothing will come of it anyway. Still, I did not ask you to rescue me from wasting my time, and if that's your opinion, then you're entitled to it, but you're not at all entitled to stifle my concerns or decide for Eleon whether or not my bug report is worth their time.
So again, I honestly don't understand the point of all this. You've identified the problem and offered a workaround, which is great. There is literally no need for you to go any further by declaring the bug fixed when I am specifically looking for a permanent Dev solution and not a temporary user workaround, as you now admit the real problem you have is that you think the devs won't fix the bug and that we'll all have to use your solution. So again, if it's all the same to you I'm happy to allow the report to remain open in hopes that the Devs can address it in due time, as my post was directed to them and not you. I'm now going to re-post this bug report as you've basically derailed and soured this entire thread and ensured nobody will ever read it due to all the wasted space you're arguing has caused. I will include a link to your workaround with the note that it is not a permanent solution, while still asking for the Devs to address the issue in their own time if they are so inclined. I expect you will refrain from attempting to derail that thread as well and thank you ahead of time for respectfully doing so.
I just don't think they are aware of the issue.
And they won't be made aware of the issue if Kamen Cider keeps ♥♥♥♥ blocking my bug report (and posts in other threads) by trying to say there is no bug.