Which IPs is Beamdog currently actively working on?
I am unfortunately not very interested in either Mythforce or Axis and Allies.
Is there anything new in the pipeline?
Hey, all, my app stopped working after IOS auto updated last night. I figure they’ll fix it. But anyone know how to extend my time to play while they do fix it? Many thanks fir any guidance in this!
I’ve noticed an influx of people with this problem (for Axis & Allies 1942 Online on iOS) over the weekend, for one reason or another.
We’re still working on the issue, it’s getting closer. If you join Discord, you’ll be able to get a special role related to the issue and get notified once we start a test. https://discord.gg/QGBpdjptsT
@JuliusBorisov I've been paying attention to the recent developments with Embracer Group rebranding itself as Fellowship Entertainment. My question is, How will this "new phase" affect @TrentOster's and @CameronTofer's company, and more importantly, how will it affect our gaming community going forward? In case I had to clarify, this is not an attempt to "reach out" to anyone. This is a legitimate concern. I am genuinely concerned for Beamdog's state of affairs. I can't speak for everyone else on this forum, but I think we all are.
@JuliusBorisov I know this is a shot in the dark but I (and I'm sure others) would appreciate the chance to get a physical copy of the BGEE Adventurer's Guide manual that came out with the Dragonspear DLC. The few that were printed with the collector's edition are basically impossible to find, and it is the only complete manual to classes/spells out there. I would even be thrilled with just a Print On Demand version we could buy that, depending on who you go through, might not cost you anything upfront and allow us to give you more money. Just a thought from a humble fan.
Business as usual. The Embracer rebranding doesn't affect Beamdog.
Good to know, tovarish. Glad something is actually working in Beamdog's favor. Happy Labor Day to those who celebrate it. Do they have a holiday like that in Edmonton?
Edit: Though my mind is not for rent to any god or government, I'm always hopeful yet discontent. I know changes aren't permanent, but change is. And on that note, I have to go to work. Until next time, be blessed, be safe, stay healthy.
On August 25th, 2025, GitHub Issue #524 was closed as not planned. Before closing the issue, the collaborator/developer who assigned himself to it left a comment stating, "Closed. Won't fix." He then closed my ticket as not planned, then he closed it as completed, then he reopened my ticket only to close it as not planned again. Prior to this happening, I was accused by another developer of spamming when I alerted him of a typo in the License section of his NWN Overhaul Project. He said this time I made it needlessly personal, and it was a little creepy. I tried to explain to him that I had the best of intentions, and it was never meant as spam. You'd be amazed at what people are willing to sue you for nowadays, especially when it comes to copyrights. I assured him I was only trying to help. I am highly detail oriented to a fault.
The events that transpired last week coupled with the issues I had been dealing with in real life left me feeling more frustrated than I can ever remember. And in a moment of weakness, I let my hatred for a bug overtake my love for the game. I misinterpreted what the collaborator/developer said and did as a deliberate, malicious act, and I grossly overreacted. The comment I posted contained words that most people say when they are ready to fight. In that moment, it didn't matter to me whether I got banned from GitHub or not. Nothing mattered.
The collaborator/developer who closed my ticket was generous enough to offer me a different perspective. He informed me that the process of closing issue #524 was a fumble on his part, and he apologized for the fumble. He blamed the crappy, unfamiliar GitHub interface and the fact devs can close tickets, but they can't lock them. That can only be done by someone higher in the food chain. He then began to explain their version history goes back roughly half the amount of time between now and 2006. There is nothing to gracefully do a diff on. He also explained that NWN's combat engine is "hairy code". He said that after looking through it a bit, he deemed himself unqualified to sneeze at it without introducing bigger issues. He told me that, on the dev team, he was probably my last best hope anyone would pay attention to the issue.
My question to you, Mr. Borisov is this: If the collaborator/developer closed my issue because he deemed himself unqualified to fix it, why didn't he simply state that in his comment prior to closing it? "Won't fix." sounds a lot different from "Won't try to fix out of consideration for being unqualified.". More importantly, why didn't he just leave my ticket open for a collaborator/developer deemed more qualified than he to fix the issue instead of initially closing it with the intent to lock it down?
I am neither defending nor am I excusing the way I behaved when I posted my last comment regarding the issue; I take full responsibility. That was my fumble, and I apologize. That's on me. I regret the use of harsh language in that comment; I am merely stating the fact that communication regarding the issue could have been handled a lot better on both sides. I am following the advice of that same collaborator/developer by trying to find a different perspective.
After coming to the realization this whole thing was a huge misunderstanding, I submitted an issue that really isn't an issue at all but a formal apology to him and everyone else on the Volunteer Development Team. You can read it here, sir. Again, I am truly sorry for overreacting to both my issues getting closed as not planned, especially the one I have been trying to get resolved for almost twenty years now. Please forgive me. Good night, Mr. Borisov. Be blessed, be safe, stay healthy.
Edit: I just read an email GitHub Support sent me yesterday stating that I must remove the content that got my account there flagged. Once I have done so, and if I agree to abide by their Terms of Service going forward, they will continue their review of my request for reinstatement. Problem: Beamdog locked and limited the conversation to collaborators. I cannot remove the content from what I have been locked out of. I need Beamdog to unlock it so I can remove the content. Please and thank you.
Comments
I second this.
We’re still working on the issue, it’s getting closer. If you join Discord, you’ll be able to get a special role related to the issue and get notified once we start a test. https://discord.gg/QGBpdjptsT
Good to know, tovarish. Glad something is actually working in Beamdog's favor. Happy Labor Day to those who celebrate it. Do they have a holiday like that in Edmonton?
Edit: Though my mind is not for rent to any god or government, I'm always hopeful yet discontent. I know changes aren't permanent, but change is. And on that note, I have to go to work. Until next time, be blessed, be safe, stay healthy.
On August 25th, 2025, GitHub Issue #524 was closed as not planned. Before closing the issue, the collaborator/developer who assigned himself to it left a comment stating, "Closed. Won't fix." He then closed my ticket as not planned, then he closed it as completed, then he reopened my ticket only to close it as not planned again. Prior to this happening, I was accused by another developer of spamming when I alerted him of a typo in the License section of his NWN Overhaul Project. He said this time I made it needlessly personal, and it was a little creepy. I tried to explain to him that I had the best of intentions, and it was never meant as spam. You'd be amazed at what people are willing to sue you for nowadays, especially when it comes to copyrights. I assured him I was only trying to help. I am highly detail oriented to a fault.
The events that transpired last week coupled with the issues I had been dealing with in real life left me feeling more frustrated than I can ever remember. And in a moment of weakness, I let my hatred for a bug overtake my love for the game. I misinterpreted what the collaborator/developer said and did as a deliberate, malicious act, and I grossly overreacted. The comment I posted contained words that most people say when they are ready to fight. In that moment, it didn't matter to me whether I got banned from GitHub or not. Nothing mattered.
The collaborator/developer who closed my ticket was generous enough to offer me a different perspective. He informed me that the process of closing issue #524 was a fumble on his part, and he apologized for the fumble. He blamed the crappy, unfamiliar GitHub interface and the fact devs can close tickets, but they can't lock them. That can only be done by someone higher in the food chain. He then began to explain their version history goes back roughly half the amount of time between now and 2006. There is nothing to gracefully do a diff on. He also explained that NWN's combat engine is "hairy code". He said that after looking through it a bit, he deemed himself unqualified to sneeze at it without introducing bigger issues. He told me that, on the dev team, he was probably my last best hope anyone would pay attention to the issue.
My question to you, Mr. Borisov is this: If the collaborator/developer closed my issue because he deemed himself unqualified to fix it, why didn't he simply state that in his comment prior to closing it? "Won't fix." sounds a lot different from "Won't try to fix out of consideration for being unqualified.". More importantly, why didn't he just leave my ticket open for a collaborator/developer deemed more qualified than he to fix the issue instead of initially closing it with the intent to lock it down?
I am neither defending nor am I excusing the way I behaved when I posted my last comment regarding the issue; I take full responsibility. That was my fumble, and I apologize. That's on me. I regret the use of harsh language in that comment; I am merely stating the fact that communication regarding the issue could have been handled a lot better on both sides. I am following the advice of that same collaborator/developer by trying to find a different perspective.
After coming to the realization this whole thing was a huge misunderstanding, I submitted an issue that really isn't an issue at all but a formal apology to him and everyone else on the Volunteer Development Team. You can read it here, sir. Again, I am truly sorry for overreacting to both my issues getting closed as not planned, especially the one I have been trying to get resolved for almost twenty years now. Please forgive me. Good night, Mr. Borisov. Be blessed, be safe, stay healthy.
Edit: I just read an email GitHub Support sent me yesterday stating that I must remove the content that got my account there flagged. Once I have done so, and if I agree to abide by their Terms of Service going forward, they will continue their review of my request for reinstatement. Problem: Beamdog locked and limited the conversation to collaborators. I cannot remove the content from what I have been locked out of. I need Beamdog to unlock it so I can remove the content. Please and thank you.
~ Prince_Raymond