Thanks to the proliferation of portable devices, a lot of people no longer need a printer for "regular" printing at all in 2026, and some of the more interesting printing substrates either don't accept toner well or won't survive the heat of a laser printer's toner setting stage.
Also, while the technology is theoretically simpler, it may be harder for an individual to source or make the physical components like rotating drums and high-res LED arrays.
There are even rumors of a Final Fantasy VII reboot!
Final Final Fantasy VII?
"rd" and "rmdir" only work on empty directories in MS-DOS (and I assume, by extension, in Windows shell). "deltree" is for nuking a complete tree including files, as the name suggests.
Very similar variants of the same CPU and VDU were used in the Colecovision, the MSX, and Sega's early systems, among others.
I've also read that there were several ports from the ZX Spectrum to the MSX, due to them sharing essentially the same CPU at the same clock speed, and the MSX VDU having a video mode that could operate similarly to the Spectrum's display.
What ShinkanTrain said. The last a read about it, the PS2 only switches into PS1 mode on a trigger from the optical drive subsystem, and then most of the memory and other hardware used to run homebrew is deactivated. AFAIK no-one's yet found a way to trigger the change in software and keep the connection to wherever you're loading your game from.
I believe that on certain revisions of the console, MechaPwn can overcome the protection, but you still need a "Playstation 1" CD in the drive to actually run something, as ShinkanTrain wrote.
I use 10ten (previously Rikuchamp) for Japanese. I don't think it does full translation, but it gives thorough dictionary lookups (from WWWJDIC) as mouseover tooltips. Very useful if you're trying to learn the language, but maybe not so much if you just want to read stuff quickly. I think it's now available for every major browser, but I mostly use it on FF.
I apologize, because between OP's post and looking at the OnlyOffice website, I got the impression that it was only a web app, requiring a web server to run. After reading another comment here I looked harder on the website and found the download links for the standalone versions.
Ha ha, it certainly does look like it, doesn't it? Kind of like how Sega would put their consoles into various games for fun, like as parts of the robots in the Virtual On series, or the backpacks in Typing of the Dead.
Ah, OK! Well, even if you're writing your game in JavaScript, there's still no need to work with the data directly as a JSON object. JS has built-in functions for serializing stored objects into JSON format (After all, the "JS" in "JSON" stands for "JavaScript"). If you aren't using JS, working with your data in a JSON representation seems like unnecessary overhead.
I think that one very common approach would be to make a simple array of objects for each "container" (this includes the player character and NPCs). Exactly what those objects are would vary by your language, platform, and personal tastes. You could have objects which contain all the information associated with themselves, such as name, description, weight, etc., or they could be as simple as an ID code that is an index into another table, and a count of how many of that item are held (this can reduce the likelihood of bugs).
The objects could also have their own methods such as reporting the weight or value of the item, which may simplify things if one property of an item (e.g. resale value) can sometimes be affected by another (e.g. level of wear), but not always. Or alternatively you could have functions that query the item objects and do all the necessary calculation and adjustment externally.
That's if your objects are mostly copies of the same things (e.g. health packs, ammo). If your objects are mostly unique (e.g. key, to room 102, Michael's pencil), many people instead make a single array which contains every object in the game/level, and each object includes a "location" attribute, with values such as in the player's inventory, in a particular NPC's inventory, or at a spot in the game world (perhaps specified in another object attribute). This can reduce the chances of accidentally creating multiple copies of "unique" items.
With regards to saving, if you're using JS then you can just automagically serialize your top-level array(s) to JSON and save that to a file. If you're using another language/environment, you'll need to figure out a file format that suits you, or look for a library. Making your own file format shouldn't be too hard, because a file is just a big array of byte values, and presumably you don't need to worry about interoperability.
I think that a game has to be "purchaseable" for $0 to have a "claim" option. If it's just "free", it won't have a "claim" option. Some authors seem to switch this setting on purpose to stop people from keeping free download access to their game after the free period has ended. Sure, we could just keep the files backed up ourselves, but a) how many people really do that, and b) the author could release updates and DLC later to encourage a purchase.
This is fantastic. I've never had a real problem claiming the giveaways before, but today I had the same issue you described, and I remembered this post. Thanks for sharing!
Only if what you are printing onto is regular paper. My contention is that since printing itself has become a somewhat niche act for individuals printing at home, they're more likely to be printing for specific reasons, which means that they're more likely to want to print things like transfers or other specialized substrates that may not work well with laser printing.
Yes, I believe that laser printer toner lasts longer than fluid ink, although ink can last for years when stored in a properly sealed bottle rather than in a cartridge inside the printer, which is possible with a user-fillable cartridge.