If you are a beta tester for the new versions of the Wave Katana or the Taketori Katana, you will now find that previous Beta versions no longer work.
When you attach an older Beta, you will get a chat message stating that "This product version has been permanently disabled", and the sword will permanently cease functioning. You will automatically be sent an updated version of that weapon, which will operate normally, until the next version comes out.
This is being done for two reasons:
- It can help me correlate bug reports with weapon versions. I have beta testers from all over the world, and language barriers can cause confusion about which product version contains which bug. Such problems can be mitigated by ensuring that all beta testers are using the exact same version.
- I need to test the ability to disable old versions of weapons. There are far too many people out there intentionally using old versions of C:SI weapons, and simply ignoring updates. There are many obvious problems with this, and having the ability to force users to upgrade provides me with much more peace of mind.
Please keep in mind that this ‘forced upgrade’ is not going to be the standard method of upgrading in the future. For the most part, updates will continue to be delivered as they have always been delivered in the past. But for this beta testing cycle, I need to ensure that this functionality works as designed.
10 Comments
I have a question.. since beta taketori/wave aren’t compatible with other katanas(Musashi,Arch, Ash), how will we know if the speed/damage/kick push are balanced? Wouldn’t it be better if we release the update first so we can test out other weapons as well just in case if other weapons need fixes too, not just Wave/Taketori.
Greetings. The update function is functioning. I think so.
When I did V2.1 in rez, the message was displayed.
“[15:42] Wave Katana V2.1 BETA (Boxed) BETA Feb 21 2009: You may now delete this product box”.
The error dialog was displayed, when I ignored warning and try to attach and use katana.
“Wave Katana V2.1 BETA Jan 21 2009: This product version has been permanently disabled.”
“Wave Katana V2.1 BETA Jan 21 2009: Could not find script ‘Attack’.”
The error dialog was displayed, when I equipped with V2.1 and did tp.
“Wave Katana V2.1 BETA Jan 21 2009: Updates: (426) You must now upgrade your weapon”
Masmako, did you receive a new “Wave Katana V2.1 BETA (Boxed) Feb 27 2009″?
Thank you for testing the beta, I appreciate it.
Yes, that would be ideal.
Unfortunately, it’s just a reality of the sort of online, geographically distributed way that we work that not all of the C:SI devs are always ready at the same time.
I know that the other devs are nearly ready to release the update, but in the meantime I have an obligation to ensure that my own weapons are without obvious bugs.
We don’t really expect any compatibility/balance issues since very little is changing, but should any such issues arise you can be sure we will address them with all due haste.
Greetings. Yes, Thank you for sending new wave(“Wave Katana V2.1 BETA (Boxed) Feb 27 2009″).
Just had a problem with the Take Beta
196.98,215.98
On this region
Taketori katana V1.5 Beta Feb 27 2009: Unable to create item
a73fa09e-3fdb-904f-37db-2b92c3d65583 that has caused problems on this region
And by the way
the third kick deosnt show up when my ao is on
I dont fight with my ao on so its not a big issue for me.
But i thnk its worth montioning.
WTF? I tried looking up that error message, and as best as I can figure it means that Second Life is borked. There doesn’t seem to be any legitimate case of receiving that message that I can find.
But… What exactly is it supposed to mean? Because I can pretty much guarantee the Taketori has not caused problems in any region, and apparently there is nothing for me to do about it.
If this is happening more than just an isolated incident or two, the only thing I can think of is to file a JIRA about the issue.
Kenshin and I were trying out Kicks with the Take’s and the entire region froze. No one could move for about 30 seconds. Spars were stopped in mid slash. But some of us could communicate. Very Strange. It probably is SL. As a test, we will try to reproduce this failure tomorrow. I will let you know.
There are a number of VERY serious known issues with Second Life servers right now, and it’s hard to know sometimes what the cause of any particular problem is.
Please do try to reproduce that. I suspect it will not happen again, but it’s certainly worth trying.