kurzih

This is not a guideline, but rather what I would recommend myself: File Size: There is a limit in size. You can't upload files too big, the system will give you an error when trying to do so or if the file format is wrong. File Quantity: That Limit is probably just common sense. 2-6 Gameplay screenshots sounds like a good number to me - I usually just upload the title screenshot and 1-2 gameplay images, especially if one screenshot can be 5Mb. I don't think many would want to see their HD filled up too quickly I wouldn't add more screenshot images where there are screenshot images already. But you can always try to submit a replacement to existing ones if you have for example a higher quality one, or with the correct aspect ratio expected for the platform. Or replace one that has a watermark (which is against the database rules). Thank you for wanting to contribute! It would be great having more media especially for PC games, looking forward to it

Looks like the same as I wrote about in my "random bug: duplicate entries in certain conditions?" topic a while back. Your links are: https://gamesdb.launchbox-app.com/games/details/131705 and https://gamesdb.launchbox-app.com/games/details/131706 Totally same behavior: those are made one after the other. I suspected that on my part I had either timed out the system if that is even possible (I check a lot and get as many pictures I can, remove backgrounds on discs etc. while I'm submitting) or a couple of times had to go back with my browser to the "add new game" page because I clicked another page by accident. I suspect those "tandem entries" are seeing by the system as one entry by a submitting user but are made twice in the system, one with images and texts and one with just texts (or part of the texts). They don't seem to get deleted even if approved, maybe because they are "linked" or seen as "one" with the entry that was approved (in your case 131705 seems to be "married" with 131706). If it would help I could search for similar entries from my cases, they are still there. Like the one in my topic. Well it's a mystery to me, but I've seen this pattern quite a few times. Maybe someone has a better analyze of this case

The answer is in the rules: "The release date should be the first date the game was released on." And since the NES platform in the LB database includes Famicom games as well ("same console", different region), the date is correct. I can only think of having "Alt release date + region" as a new option to change that. https://en.wikipedia.org/wiki/Donkey_Kong_(video_game): Famicom/NES: JP: July 15, 1983 NA: June 1986 EU: October 15, 1986

Here he/she goes again:

Sounds very much like the same person(s) I reported a few weeks back. Jason took care of it, but I guess they seem to find ways back I'm afraid. I'm sure most DB moderators just rejected those, since they are quite obvious - I only saw one case an hour ago and rejected it too. It is annoying and a waste of time in the other hand. The database is a very important part of what makes the Launchbox/BigBox experience so great. And it's been polished everyday.

Did you check the option with Mame using autoboot? That might be a solution/alternative. vg5k -skip_gameinfo -autoboot_command "cload\n" -autoboot_delay 3 -cass

Yu-Gi-Oh! Dark Duel Stories, released in Japan as Yu-Gi-Oh! Duel Monsters III: Tri-Holy God Advent in 2000. (International version in 2003). Yu-Gi-Oh! Duel Monsters II: Dark duel Stories: released on July 8, 1999 in Japan; it was never released internationally. The first international version looks to me to be the the 3rd game that came in Japan. Reminds me of Final Fantasy numbers etc. Just uploaded the cover/back cover for the Japanese version of Yu-Gi-Oh! Dark Duel Stories (aka Yu-Gi-Oh! Duel Monsters III in Japan) Edit: also submitted to remove the wrong alt name (Monsters III) from Yu-Gi-Oh! Duel Monsters II

Looks like two separate games: One from 1998 and the second from 2000. Also the subtitle on the title screenshot for Karamuchou wa Oosawagi! Okawari!. Okawari! = Seconds! (indicating a sequel or "definitive" edition). NP = Nintendo Power, more info on that: https://en.wikipedia.org/wiki/Nintendo_Power_(cartridge). Actually Karamuchou wa Oosawagi! Okawari! (カラムー町は大さわぎ！おかわりっ!) looks like it was released via NP only, not as a cartridge, thus the fan art - front box.

On my part I only managed to get into Integer basic mode without pressing anything like this: apple2e -skip_gameinfo -autoboot_command "INT\n" -autoboot_delay 12 -flop1 "PATH TO IMAGE DISK dos33mst.dsk" -cass Notes: this partial solution works with the Apple II/e model and I loaded "Apple DOS 3.3 BASICS (1980)" disk to do that. Main issue (same as yours): the cassette does not start itself when writing "LOAD" after the "INT" which is executed fine with autoboot. The game I got to work was the cassette game bomber1.zip. But I needed to manually start the tape and then wrote "LOAD", waited, and then wrote "RUN" to finally get the game running. Hopefully this might give a clue to a solution where everything is automated, but I doubt we might find one since cassette loading times differ and we need that "run" command after the program has been loaded.

Let's submit them, we have all the info and media we need from the Arcade section, right? I'll start doing it with Sega Model 1 as I just rejected a move from Star Wars Arcade => Sega Model 1. Might as well do the new entry myself. Of course if there would be a "copy to platform: X" or other way to keep the original entry where it is, but have it copied to another platform. that would make things a lot faster. Edit: and in the process we might fill some gaps in the metadata and find more images - like the arcade cabinet etc.

Hi @fordgt68 Just wanted to personally thank you for your contribution! C64 was my first computer, really appreciate your effort! It looks you're not far away from getting everything done with C64, compared to what's behind you already. I've actually started to make my own "platform" list for Commodore 64 Demos and I already made a Launchbox "platform" list of a few thousand Commodore Amiga demos & Intros, with screenshots, logos, backgrounds etcs. Too bad we can't use them directly in the Database, but maybe I could share those if someone finds them interesting.

I agree with a lot of suggestion here! For me I would be already happy for just a solution for this case @Jason Carr: Ideally games with identical names in the same platform (but are not the same game) could all be found from the database and all images would not get mixed up <= this is the biggest issue, media getting mixed up (since after downloaded, the images take their name from the default title name in our images folders). And not forgetting about EmuMovies manuals and videos, where it gets even more complicated if there are titles named the same. So far this has been a workaround fixing it within the database: "Proper title name (Publisher)" or if not possible "Proper title name (Year)" + ALT names as "Proper title name" and all variations to make it possible for the search function to find it. So this would name the title with a unique name, but still keeping the proper name it should have according to the database rules. Might be ugly looking, but at least it works for now. Here's a good example of the problem, as long as no one has fixed it yet, until you read this: 1. Choose the Commodore 64 platform and press "Add" and search for: "Battleship" in Launchbox App 2. It should give only one result: Battleship (1/1/1988) ID: https://gamesdb.launchbox-app.com/games/details/88189 - not the most well known battleship game for C64 I might add. In reality there are this amount of games called Battleship for Commodore 64 in the database, but only one can be found in the app, because they all have the same main name: https://gamesdb.launchbox-app.com/games/details/88185 https://gamesdb.launchbox-app.com/games/details/88186 https://gamesdb.launchbox-app.com/games/details/88187 https://gamesdb.launchbox-app.com/games/details/88188 https://gamesdb.launchbox-app.com/games/details/88189 https://gamesdb.launchbox-app.com/games/details/113365 https://gamesdb.launchbox-app.com/games/details/32326 (this is the one I would have wanted to add, from Elite/Epyx etc.) Adding unique names (as the workaround above) to those, like "Battleship (Dynastar)" and as alt name "Battleship", would make the app find that entry when searching for "Battleship", and also download images/media that will not get mixed with the other titles called battleship. If a more technical/program based solution is found with .dats/hashes or something else and we could do without that "Game name (Publisher)" solution, that would be superb! Though I don't really mind having titles named like that as long as they are found in the app and the images are correctly united with their games. Emumovies videos & manuals are another topic since they tend to behave even more problematically with titles named the same. The workaround so far for that is quite manual and on the user's side (making a copy of one video and downloading again for the other title(s) and then renaming the copy back to the one that was replaced/overwritten.. something like that :D). EDIT: updated entry to reflect the latest development: The Main Default name still needs to be unique on the same platform, but the Alternative name cannot be identical anymore/cannot be used as it was since it will not show up if there is multiple identical alternative names.

I without any doubt agree with you on the unique naming part and usage of common sense. I also just posted about this issue we were talking about earlier in the troubleshooting: it's a very Déja vu feeling when we've just fixed something a few weeks ago and badaboom, someone tries to unfix them. Of course I don't believe that it's meant to be on purpose to mix things up. Thankfully there are some great experienced database moderators doing a great job every day and motivated new ones as well - and the contribution is stellar, the database is really fantastic. But as you said it only takes 3 new moderators who aren't familiar with all the stepping stones that might turn a few hair grey on the ones who had fixed something before

No prob! Sorry nothing here. I did try to find out if that would be possible earlier and I suspect my skills for coding some "sendkeys" would have hit the wall anyway That would have saved a lot of command lining indeed But do tell us if you manage to find a way!

I have to say, while just moderating a minute ago someone AGAIN is trying to mess the database up by changing the unique game names for games that happen to have the same name on the cover/screen title. If that goes through we will have duplicated names in the database and big issues: If there are titles named, under the same platform, exactly the same, they will be messed/mixed up with images, since the images/media are saved based on the game's name. And second, the search function will not find all the entries with the same name, it will probably display only the one that is first in #ID order and ignore the others named the same. What's important: - Title names must be unique under the same platform, and what has been used (a lot of moderation work behind that, I thank those for doing it!) works well enough: "TITLE NAME (PUBLISHER) or in some cases if publisher happens to be the same: "TITLE NAME (YEAR)". - The actual "proper" name, like "Alien" can be added as the ALT name - it will actually help the search function find those "TITLE NAME (PUBLISHER)" if for example the rom file is not named like that - but many collections actually are using "game name(publisher)(year)" to distinguish different games under the same title name. Do correct this information if I'm wrong, but this is what I've been experiencing. EDIT: updated entry to reflect the latest development: The Main Default name still needs to be unique on the same platform, but the Alternative name cannot be identical anymore/cannot be used as it was since it will not show up if there is multiple identical alternative names.

You're welcome! There indeed isn't probably many Apple IIGS games that require that. I'm afraid I don't have a proper answer/list of games that do. There was the unreleased Shuffle Puck Cafe that probably requires the OS too (says unable to load ProDos otherwise). But I would think that many that don't need the OS do still work with the OS option, if one doesn't mind clicking the game from the OS to start it. As I said, that was just a "bonus" command line . I have this option as the default command line and if a game wouldn't work then I'd use a custom command line without the OS. Probably a matter of preference and I kind of like the old school 6.01 IIGS OS. I don't mind loading from there. EDIT: maybe the "none boot" mention (from the game files' name) in the TOSEC IIGS collection might work for a list of games that requires the OS.

Hi! Here's a few more I've been using myself, so why not share them too. Some are useful for floppies some cassettes only: Sharp X1: x1 -skip_gameinfo -autoboot_command "CHAIN”“\n" -autoboot_delay 9 -cass (You need to be careful with the ”“ they are not "" :D) Sam Coupé: samcoupe -skip_gameinfo -autoboot_command "\nBOOT\n" -flop1 BBC Micro: bbcm -skip_gameinfo -autoboot_command "*tape\nchain""""""\n" -cass Camputers Lynx: lynx128k -skip_gameinfo -autoboot_command "mload""""""\n" -cass Matra & Hachette Alice: alice90 -skip_gameinfo -autoboot_command "cload\n" -cass Memotech MTX512: mtx512 -skip_gameinfo -autoboot_command "load""""""\n" -autoboot_delay 3 -cass Philips VG 5000: vg5k -skip_gameinfo -autoboot_command "cload\n" -autoboot_delay 3 -cass And Bonus for Apple IIGS for floppy games that need to boot from OS: apple2gs -skip_gameinfo -flop3 "PATH TO System 6.0.1 DISK IMAGE" -flop4 Apple II floppies boot fine (at least the ones I've tested) without autoboot: apple2ee -skip_gameinfo -flop1 Good night!

To be honest, I'm not really an expert on Electron (my first computers were C64 and Amiga - as you might guess from my avatar xD). But I think there's no "one command line" to rule them all with Acorn Electron I'm afraid. Some dumps work better than others it seems too, I think that on original hardware you might encounter bad program errors as well. And the emulation in Mame isn't quite finished yet to my understanding. But it's been nice figuring stuff out and thank you for your help as well! I really like to get my setup as automated as possible and as working as possible. One of my nicest things I figured out, was PC-98 CD titles to work with launchbox - Policenauts with CD audio and Space Pirate Harlock with boot/title floppies etc. that felt like a big win when I got them working

Great find with the expansion's options guys! Did you try with the EXEC command instead of RUN (which is used to execute for machine coded !BOOT files) for egghead: electron -exp plus3,bios=4 -skip_gameinfo -autoboot_command "*cat\n\n\n\n\n\n*exec !boot\n" -flop and you can add the delay if you need to that command of course. I made it to the title screen at least EDIT: (Though I am using a different dump that seems to work better, but didn't work either with the RUN command, but did with EXEC).

You should see the content of the disk after the *cat, since it will show the disk's directory. There's plenty of ways to load disks, that one just worked with the three I tested them on. You had the -flop in the end, right? Since that would put Mame to mount the disk first, otherwise there's no catalog to load.

No prob! I tried with the few floppy images I have on Electron and put this custom line for floppies; seems to do the work so far (as long at there is a !boot in the disk): electron -skip_gameinfo -autoboot_command "*cat\n\n\n\n\n\n*run !boot\n" -flop I put a lot of returns (\n) so that it could have time to load the catalogue and execute the command after that.

I don't know if the retroarch core has the autoboot implemented and how to use it with that setup. I'm using the latest Mame exe with Launchbox from https://www.mamedev.org/release.html https://docs.mamedev.org/commandline/commandline-all.html : -autoboot_command "<command>" -autoboot_delay [n] -autoboot_script / -script [filename.lua]

In Retroarch/System. But many cores can work without them, I think you can check the requirements here: https://libretro.readthedocs.io/en/latest/library/nestopia_ue/ I think I found your issue, from that link there is this warning: Nestopia UE requires the NstDatabase.xml for general proper emulation. Make sure it's in RetroArch's system directory. Filename Description md5sum NstDatabase.xml Nestopia UE Database file - Required disksys.rom Family Computer Disk System BIOS - Required for Famicom Disk System emulation ca30b50f880eb660a320674ed365ef7a And to double check also: Is you system in Launbox called "Nintendo Entertainment System" as it is in the associated platforms? If it's a different name (like just NES), then it won't find the proper core. EDIT: the NSTdatabase.xml link doesn't work for me at libretro's docs, but there's been a conversation here in the Forum where you can find it:

Can't think of much here, unless there's a bios missing