- Posts
- 761
- Likes
- 662
did u guys give up cause like their hasn't been a new dueling build in like 3 years haha what is eta on tempest build open beta
hello movie 2 developers where is dueling patch
- Thread starter RogueWookiee
- Start date
Hessu
Internal Beta Team
- Posts
- 798
- Likes
- 1,308
Last ETA was late november
D what a fool i was to believe it. Last time when there was actual saber testing was 3 years ago lol
- Posts
- 1,046
- Likes
- 1,518
It will go to open beta when we are ready. There has never been a firm date and this kind of thing makes me wonder if it would be a better idea to go back to not talking about time scales at all.
What needs to happen to get the open beta out is this:
I would say that will be atleast 4 to 8 weeks. I would not surprise if it was longer if we hit issues or time constraints.
What needs to happen to get the open beta out is this:
- Finish new launcher
- Migrate all users to new launcher
- Wait a brief stability period to make sure everything is working
- When Tempest has the code working on the latest build run the open beta
I would say that will be atleast 4 to 8 weeks. I would not surprise if it was longer if we hit issues or time constraints.
Leo
Internal Beta Team
- Posts
- 329
- Likes
- 379
as a matter of fact no, was obviously a bait like it has been for past few years4 weeks later...
WTF DEVS YOU PROMISED TEMPEST PATCH IN 4 WEEKS
- Posts
- 761
- Likes
- 662
i honestly feel bad for the devs who worked on CTF only for no one to play it lol
Leo
Internal Beta Team
- Posts
- 329
- Likes
- 379
i feel bad that this was the 'REASON' why tempest build wasn't even near beta
Leo
Internal Beta Team
- Posts
- 329
- Likes
- 379
Well it was told to me that you (devs) can care about tempest once u finish CTF
- Posts
- 1,046
- Likes
- 1,518
Not exactly. Different people work on different things. It wouldnt have been right to hold up CTF when there were other things that differnt people needed to do to get Open Betas ready - namely launcher. Since you were not one of the two people who gave test feedback on internal beta launcher release before the current one - that makes you one of the people who has held the Open Beta up. I hope you appreciate the irony of complaining about something you could help to bring about but just cant be bothered to.
Hessu
Internal Beta Team
- Posts
- 798
- Likes
- 1,308
I was under the impression that the duel build was ready for open beta but you decided to make ctf your priority and run ctf open beta first. Which is a shame seeing how it died shortly after release. There is not even official ctf servers
Leo
Internal Beta Team
- Posts
- 329
- Likes
- 379
Mace would slide into this conversation saying "But that was never the plan (CTF being popularized). It works only as submode which is good enough"
- Posts
- 1,913
- Likes
- 2,672
Like defiant said, it was not. CTF was started before tempest build did, and has been in progress longer as a result. Also it was Redsaurus, Spaghetti, and I that mainly worked on finishing up CTF stuff. Tempest is the only one that is currently working on his saber stuff.
This entire thread just makes me sad though, cause its full of misreading the words of devs to intentionally cause problems between us and the community. My estimates are generally based on everyone having adequate time to work on things each day and that isn't always the case. I often use words like hopefully, in order to convey its an estimate. Having my words taken as a guarantee when I did not word it like that doesn't help things. I also said many times that CTF open beta was a trial run of the launcher, to prep for the larger open beta for the saber system. Not that "once ctf is done we can care about saber build" because that isn't what I said and I have frequently said that the two are not reliant in any way on one or the other.
As far as I am aware, it is more or less ready for open beta, but the launcher is not. We ran CTF open beta to get more eyes on the launcher to help get rid of the bugs, without impacting the more important saber open beta and so that it could be smoother when ran.