Game Localization Writer | Author, The Legend of Zelda - A Complete Development History | @ZeldaWiki | Prev: PM @Zomato, Writer @GIBiz, EiC @Siliconera
SR388
Joined September 2008
- Tweets37.1K
- Following657
- Followers1.3K
- Likes558
Ishaan Sahdev retweeted
15年くらい前に凄腕アシスタントの先輩に教えてもらったフリーハンドのかけあみ。
著名&超絶画力職場を渡り歩き、スピンオフ作品などもその作家さんに合わせて描けたりと、スキル超絶高い人だったけど、もう業界引退したらしくて少し寂しい。
Ishaan Sahdev retweeted
As high-profile websites vanish, it’s a reminder that the web has no built-in archival layer.
But some publishers are now blocking the Wayback Machine.
What’s at stake if the web stops being archived? Our new FAQ explains: preserving the public record matters. 🌐📚 help.archive.org/help/faq-pu…
Ishaan Sahdev retweeted
lol link to source since these wannabe aggregators can’t read to save their lives
substacktools.com/sharex/WLN…
Nintendo is reportedly officially entering the Indian market in 2027 with the Nintendo Switch 1.
news.abplive.com/gaming/nint…
Ishaan Sahdev retweeted
The aiming reticle, auto-aim on the cards, the jump indicator, and lots of other design features were meant to ensure that anyone could play American McGee's Alice. And the conversation during development around difficulty and what made "a game a game" was one of the more contentious topics.
There was a programmer on the project who felt strongly that more demands should be made on the player - that ammo should be made scarce and that enemies should be harder to knock down. At one point, the game was tuned this way - since this guy controlled the code that dictated the tuning - and the enemies became damage sponges.
If I recall correctly, we waited until this guy was out at lunch one day and re-tuned things to feel more casual. When he returned, we told him not to change it back. There may have been some additional words said to make that request stick. He wasn't happy.
So when I see people talking about how difficult the game is, I wince. That is the opposite of what I had in mind. Though it should be noted that some of the notoriously difficult spots (looking at you 'river through the vale of tears') had more to do with physics/engine limitations and less to do with intentional design choices. Sometimes, even the tech will fight you to make things harder 😂
As I said in another tweet on this topic recently, different people have different ideas of what constitutes a "game" for them. And even within a given development team, not everyone is going to agree. It's also the case that even when this is "my" game, I was not able to get a 1:1 translation of my intentions into the final game.
Ishaan Sahdev retweeted
Okay everyone, its time for my last game to launch (on 22 April). After 40 years in the industry I love with all my heart, this is the most significant event in my life (other than the birth of my son). All I ask is for you to be curious enough to give it a try.
youtube.com/watch?v=xdaX_OIa…
wishlist on steam: store.steampowered.com/app/3…
Ishaan Sahdev retweeted
Yorhel has passed away
He was known for running vndb, a website he created back in 2007
The moderation team is working to preserve the website but cannot provide details at the moment
Ishaan Sahdev retweeted
For your enjoyment, the Superman screenplay.
superman.com/script/superman…
Ishaan Sahdev retweeted
Very cool to see Detective Instinct officially in the New Releases tab on Metacritic!
If any more press are interested in covering the game, send us an email at [email protected] 👀
Ishaan Sahdev retweeted
IFF's Statement on the Sanchar Saathi App Pre-Installation Directive
The Department of Telecommunications (DoT), specifically its AI & Digital Intelligence Unit (AI & DIU) on 21st November, 2024 has under the Telecommunications (Telecom Cyber Security) Rules, 2024 issued a sweeping Direction mandating the pre-installation of the Sanchar Saathi mobile application on all mobile handsets manufactured or imported for use in India. As a preliminary matter the DoT has yet to by itself disclose the full text of the direction. Initial reports by Reuters revealed it's existence and subsequently it's full text was disclosed by Medianama which form the basis of our statement, which will be followed up by RTI, analysis as well as steps, if required to support a challenge to it in a court of law.
The direction by requiring manufacturers and importers of mobile handsets to pre-install the Sanchar Saathi App represents a sharp and deeply worrying expansion of executive control over personal digital devices. The stated objective of curbing IMEI fraud and improving telecom security is, on its face, a legitimate state aim. But the means chosen are disproportionate, legally fragile, and structurally hostile to user privacy and autonomy. Clause 7(b) is the clearest expression of this. It requires that the pre-installed Sanchar Saathi application be “readily visible” and that, “its functionalities are not disabled or restricted.” In plain terms, this converts every smartphone sold in India into a vessel for state mandated software that the user cannot meaningfully refuse, control, or remove. For this to work in practice, the app will almost certainly need system level or root level access, similar to carrier or OEM system apps, so that it cannot be disabled. That design choice erodes the protections that normally prevent one app from peering into the data of others, and turns Sanchar Saathi into a permanent, non-consensual point of access sitting inside the operating system of every Indian smartphone user.
Viewed through the lens of the Supreme Court’s judgment in K.S. Puttaswamy (2017) that reaffirmed the fundamental right to privacy, this structure cannot pass the proportionality test. K.S. Puttaswamy requires that any intrusion into the right to privacy must meet the standards of legality, necessity, and proportionality. Even if we assume legality and necessity for the limited purpose of checking the genuineness of devices, the order clearly stumbles on proportionality. The government’s own ecosystem already offers less intrusive means to verify IMEI numbers and detect fake handsets such as the Sanchar Saathi web portal, SMS-based KYM (Know Your Mobile) services, and USSD codes all allow a user to perform this task without a permanent app baked into the firmware. There is no technical explanation in the order for why a one-time or occasional verification exercise justifies a resident, non-removable application with elevated privileges that lives on the phone for the lifetime of the device. Forcing a permanent app installation for a sporadic verification function is not a marginal overreach; it is a textbook example of disproportionate state action under the Puttaswamy standard.
The problems deepen when we look at the scope and safeguards. The order invokes “telecom cyber security” as a catch all justification, but it does not define the functional perimeter of the app. Clause 5 of the Directions refers to identifying acts that “endanger telecom cyber security,” an expression so vague that it invites function creep as a design feature, not a bug. Today, the app may be framed as a benign IMEI checker. Tomorrow, through a server side update, it could be repurposed for client side scanning for “banned” applications, flag VPN usage, correlate SIM activity, or trawl SMS logs in the name of fraud detection. Nothing in the order constrains these possibilities. In effect, the state is asking every smartphone user in India to accept an open ended, updatable surveillance capability on their primary personal device, and to do so without the basic guardrails that a constitutional democracy should insist on as a matter of course. IFF is deeply concerned with this direction that sets up a precedent to enforce client side scanning on all smartphones in India and calls for its recall.
As a first step we have filed a RTI with the Department of Telecom not only for a copy of this direction/order but also the underlying justification on how and why it was issued. We will fight this direction till it is rescinded.
Ishaan Sahdev retweeted
New project in the works! 🎉
Introducing TombForge - a custom Tomb Raider game engine built from scratch for the development of modern Tomb Raider levels!
Featuring PBR rendering, TRA animations, a TRAOD GMX importer and more to come! 😁 #tombraider #gamedev
Ishaan Sahdev retweeted
You know what? Let's dance, algo. Check out my new Mazestalker devlog where I talk about all these recent developments: youtube.com/watch?v=6vag12Zk…
#indiegame #gamedev #solodev #mazestalker #devlog #zelda #ys #terranigma #landstalker
Ishaan Sahdev retweeted
In an interview about Devil Blade Reboot, creator @shigatake talks about the inspirations behind the game, his thoughts on the genre, and how Devil Blade influenced 13 Sentinels: Aegis Rim! #Shmup gamedesigngazette.com/2024/0…
Ishaan Sahdev retweeted
「ENDER LILIES」は、多くのお客様からご愛顧をいただき、全世界150万本を達成いたしました。
応援いただいたみなさまに心より御礼申し上げます。
続編となります「ENDER MAGNOLIA: Bloom in the Mist」も鋭意制作中です。
今後とも宜しくお願い申し上げます。
#EnderLilies
#EnderMagnolia
Ishaan Sahdev retweeted
PROTECT THE INTERNET ARCHIVE.
It's important because you'll be able to access stuff that you can't find on the internet anywhere else. It's good for research.
If we lose Internet Archive, it would be like losing the Library of Alexandria on the internet.
PASS IT ON.
Friend of the Court Briefs Filed in Internet Archive’s Appeal — Hundreds of librarians joined prominent library organizations & non-profits in filing amicus briefs in Hachette v. Internet Archive. Read why they believe our appeal should succeed: blog.archive.org/2023/12/29/…
Ishaan Sahdev retweeted
My third book, Adventures in Games Analysis: Volume I is now available.
Purchase: danielprimed.gumroad.com/
Details: danielprimed.com/2023/10/a-n…


































