Are these new TOS Characters created recently or when the Temporal Recruitment Event was running and into August?
If the latter and these Characters were a few months old when the they did the Kit Revamp 2.0, why were they still using the Starter Kits?
My 2 affected AoY chars (Eng and Sci) were (presumbly like some other AoY's) nostalgic somehow about their initial starter kit frame and so, kept it in the bank. (allowed... Not supposed to create troubles, not so? Well, it did, though I didn't expect that to happen.) They were relatively new too, a few month old since the expansion time. Additionally, my ~level 32 non AoY Eng (fed) was an older, less played alt, not much equipped. Not that the "age" of the chars matters, like other player said. We are allowed to take a break of a char/of game or being nostalgic with items we can no longer get again, without expecting critical troubles.
Now those slots are totally non usable. Be it bank (as in my 2 AoY's case), inventory, mail, or kit frame (like it is regarding my Eng low level alt) slots, either way it's WRONG. And ignoring us (not by you but by the devs) is even more wrong.
It happened to ALL chars with starter kits at the time 25/10's (artifact expansion/kit revamp) patch, be it in their kit frame slot (worsts case. this kit frame slot is disabled then totally, which hinders the character being really damaged!), mail, inventory or bank slot, totally disabling the slot those were in. I explained why new chars were more likely to be affected, being more likely to have their starter kit kept somewhere still, as well as AoY which were (beside being relatively new) having a special non re-achievable kits some wanted to keep just in case. As added, not only new char, let alone not only AoY's, are affected.
P.S.
Some ToS char (not those with transponders) are created still and some, like the other player's here, were even very new at that patch's hit.
My Temporal Recruit had her Kit Frame blacked-out when the revamp hit and I couldn't add any Modules to the Character. It was not the Starter Kit Frame. It took me a few log outs/ins and zone switches to finally get it to clear up, but it did clear up. Frankly, I don't even remember the Starter Frame, but then again I got that Character up to 60 within a week of starting the Character so would have disposed of it fairly quickly.
This should have been fixed already. There were problems on the Tribble Test Server with the Kit Revamp and many of the problems fixed, but not enough. I just reviewed the latest Patch Notes on the Tribble Server and there is nothing about fixes for this problem. There are a number of posts there asking where is a fix for this problem which is game breaking on TOS Characters.
For your non-TOS Character a suggestion there may be to try the point mentioned in the following post extract:
'For the first bug, try the "/loot_cancel" fix. (That was the chat command to use, iirc). Do it in space first (for example ESD system space), then immediately beam down and use it in chat while on the ground. Doing that fixed the bug for me.'
'But to be logical is not to be right', and 'nothing' on God's earth could ever 'make it' right!'
Judge Dan Haywood
'As l speak now, the words are forming in my head.
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
I've posted this to the thread linked by rndflactuation
I'll add my bug here: My temporal recruit, made in the last hours of that event, and not played between then and Jan 1, has the 23c. Tactical starter kit affected by this bug.
My Temporal Recruit had her Kit Frame blacked-out when the revamp hit and I couldn't add any Modules to the Character. It was not the Starter Kit Frame. It took me a few log outs/ins and zone switches to finally get it to clear up, but it did clear up. Frankly, I don't even remember the Starter Frame, but then again I got that Character up to 60 within a week of starting the Character so would have disposed of it fairly quickly.
This should have been fixed already. There were problems on the Tribble Test Server with the Kit Revamp and many of the problems fixed, but not enough. I just reviewed the latest Patch Notes on the Tribble Server and there is nothing about fixes for this problem. There are a number of posts there asking where is a fix for this problem which is game breaking on TOS Characters.
For your non-TOS Character a suggestion there may be to try the point mentioned in the following post extract:
'For the first bug, try the "/loot_cancel" fix. (That was the chat command to use, iirc). Do it in space first (for example ESD system space), then immediately beam down and use it in chat while on the ground. Doing that fixed the bug for me.'
The REAL BUG was NOT FIXED when it was thought and said it was fixed. (BTW the Command IIRC is /LootCancel but I tried both)
We are speaking here of STARTER KIT FRAME which left characters handicaped by disabling slots, and while NOTHING HELPS. Yes, this command and map change and all were TRIED. (note that I don't know if other kit frames are still affected, I do positively know the starter kit frame issue is real and current, non fixed)
What you had is most likely an update issue (or possibly a bug which was partially fixed in your case) but the starter kit frame bug was NEVER fixed (since the kit revamp/artifact expansion patch on 25/10) despite being SHORTLY claimed so by accident / wrongly. There was no single word by a (previously affected) STARTER kit frame's owner that this bug was fixed for. There is allegedly no single starter kit frame owner (at the time of the 25/10's patch) that was NOT affected by disabling the slot the starter kit was on. And I personally can see and say it wasn't fixed - for both my AoYs and my non AoY affected chars.
Please don't say the starter kit frame bug was fixed as it was not. We want a hope to fix it so please don't do this. No offense meant. It might look that way due to frustration about a not very aknowledged bug and an urgency desire to solve the situation ASAP without further troubles/misleading devs that this was fixed while it wasn't. While devs have a very good intentions, know that not all what was ever declared fixed in past release notes was fixed (no mal-intention OFC).
I never said that the Starter Kit bug was fixed. I said that there were numerous Kit problems discovered during the pre-release testing. Many were fixed but not all.
You misread my line about 'This should have been fixed already'. It was not a declarative that this was fixed as it obviously isn't. It was written in the terms of 'This should have been fixed already, for crying out loud'. There is NO reason this hasn't been addressed by now.
That is also why I checked the the Tribble Patch Notes and said that the problem is not listed as being fixed. Why would I have said that this is a Game Breaking Bug on TOS Characters, if I thought it was fixed.
If you want me to use more all capitalized or colored words to make my point that I am on the side of getting this fixed already, I will.
No offense taken. But please don't accuse a supporter of not being so.
'But to be logical is not to be right', and 'nothing' on God's earth could ever 'make it' right!'
Judge Dan Haywood
'As l speak now, the words are forming in my head.
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
Thank you for your nice post, ltminns. I now understand.
(I don't quote it now in trying to not clutter my post more than the following issue will - )
I am really bad in words. Both expression and understanding. I apologize for not understanding you before, and no problem
In a more personal note, as it looks like it needs an elaboration. Feel free to skip though, but it explains a lot in my opinion.
The reason I color a lot is a kind of a compensation, trying hard to find and emphasize important ideas so that those won't be lost in the "sea of words" I tend to write by accident, or will be easy to locate and understand. It's usually "neutral" then. You may say it's a compensation technique/strategy on a real limitation of mine.
The color itself needs to be ideally "easy on the eye" (as possible) yet clear and distinct enough from the rest of the post, color itself may change, and if it's red or green for example it may also have a contextual meaning accordingly. Dark gray colored though are typically things I found to be less important but still decided to keep those posted without too much cluttering.
Capitalization has a similar effect, but additionally is used, especially when frustrated not to be understood or when otherwise thinking something went a -miss/might be going a-miss/non understood by others, etc, to emphasize things further yet even without coloration. (e.g. specific words) hence more charged/potentially showing frustration etc. I try not to capitalize sentences etc or "too many" words' sequence. It sounds as a real shout if I would and would offend, what which I don't want. It also might remove the desired emphasis effect. It's used more "locally" typically.
But, while re-reading that post of mine I realized it might be looking as if I tried to offend anybody (due to my frustration much capitalization was used and some words were wrongly chosen by accident), so I edited some and also clarify it was not so. This post was not meant to offend/ "going against" nobody, neither you nor nice devs who try to help both. I appreciate your help. I did post and express some valid concerns (and personally a level of urgency so to speak), as you probably saw, based on your clarification post.
<out of this topic as I should, unless things significantly changes or update in a way I can't refrain self from posting >
Comments
What difference does it make how old they were?
If they were bugged by the patch they are bugged and need fixed.
My character was made 1 to 2 days before the patch...lucky me on my timing.
Now those slots are totally non usable. Be it bank (as in my 2 AoY's case), inventory, mail, or kit frame (like it is regarding my Eng low level alt) slots, either way it's WRONG. And ignoring us (not by you but by the devs) is even more wrong.
It happened to ALL chars with starter kits at the time 25/10's (artifact expansion/kit revamp) patch, be it in their kit frame slot (worsts case. this kit frame slot is disabled then totally, which hinders the character being really damaged!), mail, inventory or bank slot, totally disabling the slot those were in. I explained why new chars were more likely to be affected, being more likely to have their starter kit kept somewhere still, as well as AoY which were (beside being relatively new) having a special non re-achievable kits some wanted to keep just in case. As added, not only new char, let alone not only AoY's, are affected.
P.S.
Some ToS char (not those with transponders) are created still and some, like the other player's here, were even very new at that patch's hit.
<pending a potential heavy edit when I have time>
This should have been fixed already. There were problems on the Tribble Test Server with the Kit Revamp and many of the problems fixed, but not enough. I just reviewed the latest Patch Notes on the Tribble Server and there is nothing about fixes for this problem. There are a number of posts there asking where is a fix for this problem which is game breaking on TOS Characters.
For your non-TOS Character a suggestion there may be to try the point mentioned in the following post extract:
'For the first bug, try the "/loot_cancel" fix. (That was the chat command to use, iirc). Do it in space first (for example ESD system space), then immediately beam down and use it in chat while on the ground. Doing that fixed the bug for me.'
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
The REAL BUG was NOT FIXED when it was thought and said it was fixed. (BTW the Command IIRC is /LootCancel but I tried both)
We are speaking here of STARTER KIT FRAME which left characters handicaped by disabling slots, and while NOTHING HELPS. Yes, this command and map change and all were TRIED. (note that I don't know if other kit frames are still affected, I do positively know the starter kit frame issue is real and current, non fixed)
What you had is most likely an update issue (or possibly a bug which was partially fixed in your case) but the starter kit frame bug was NEVER fixed (since the kit revamp/artifact expansion patch on 25/10) despite being SHORTLY claimed so by accident / wrongly. There was no single word by a (previously affected) STARTER kit frame's owner that this bug was fixed for. There is allegedly no single starter kit frame owner (at the time of the 25/10's patch) that was NOT affected by disabling the slot the starter kit was on. And I personally can see and say it wasn't fixed - for both my AoYs and my non AoY affected chars.
Please don't say the starter kit frame bug was fixed as it was not. We want a hope to fix it so please don't do this.
No offense meant. It might look that way due to frustration about a not very aknowledged bug and an urgency desire to solve the situation ASAP without further troubles/misleading devs that this was fixed while it wasn't. While devs have a very good intentions, know that not all what was ever declared fixed in past release notes was fixed (no mal-intention OFC).
You misread my line about 'This should have been fixed already'. It was not a declarative that this was fixed as it obviously isn't. It was written in the terms of 'This should have been fixed already, for crying out loud'. There is NO reason this hasn't been addressed by now.
That is also why I checked the the Tribble Patch Notes and said that the problem is not listed as being fixed. Why would I have said that this is a Game Breaking Bug on TOS Characters, if I thought it was fixed.
If you want me to use more all capitalized or colored words to make my point that I am on the side of getting this fixed already, I will.
No offense taken. But please don't accuse a supporter of not being so.
l don't know.
l really don't know what l'm about to say, except l have a feeling about it.
That l must repeat the words that come without my knowledge.'
(I don't quote it now in trying to not clutter my post more than the following issue will - )
I am really bad in words. Both expression and understanding. I apologize for not understanding you before, and no problem
In a more personal note, as it looks like it needs an elaboration. Feel free to skip though, but it explains a lot in my opinion.
The reason I color a lot is a kind of a compensation, trying hard to find and emphasize important ideas so that those won't be lost in the "sea of words" I tend to write by accident, or will be easy to locate and understand. It's usually "neutral" then. You may say it's a compensation technique/strategy on a real limitation of mine.
The color itself needs to be ideally "easy on the eye" (as possible) yet clear and distinct enough from the rest of the post, color itself may change, and if it's red or green for example it may also have a contextual meaning accordingly. Dark gray colored though are typically things I found to be less important but still decided to keep those posted without too much cluttering.
Capitalization has a similar effect, but additionally is used, especially when frustrated not to be understood or when otherwise thinking something went a -miss/might be going a-miss/non understood by others, etc, to emphasize things further yet even without coloration. (e.g. specific words) hence more charged/potentially showing frustration etc. I try not to capitalize sentences etc or "too many" words' sequence. It sounds as a real shout if I would and would offend, what which I don't want. It also might remove the desired emphasis effect. It's used more "locally" typically.
But, while re-reading that post of mine I realized it might be looking as if I tried to offend anybody (due to my frustration much capitalization was used and some words were wrongly chosen by accident), so I edited some and also clarify it was not so. This post was not meant to offend/ "going against" nobody, neither you nor nice devs who try to help both. I appreciate your help. I did post and express some valid concerns (and personally a level of urgency so to speak), as you probably saw, based on your clarification post.
<out of this topic as I should, unless things significantly changes or update in a way I can't refrain self from posting