That sounds good, for /kbin seems to generally have troubles with federating to the outside Fediverse. For example, formatted posts or posts with embedded links go out as raw Markdown code, implying that everything else can and will parse it, rather than standard Rich Text.
Also, I sometimes see posts from /kbin with a summary (the same as a content warning on Mastodon; I don't know what /kbin uses that field for), but the post in the summary is the same as the summary, only without hashtags which only appear in the summary.
"A New Regeneration Method!
NFC compatible devices such as transportation IC cards and more can be used to generate Kaiju. The NFC device will generate a unique Kaiju based on various properties. Experiment with NFC devices to find out what kind of Kaiju will be generated!"
Monster generators have spam ed from audio CDs to barcodes and now to wireless signals. Interesting to think of a bunch of kids asking to scan Mom's bus pass or throw their old amiibo on to see if they can get something different.
Most people don't actually use the NFC, It's just not as highly accessible in North America as it is in other places (Also, very specifically, Amiibos will not work, and this is an in-game notification as well. No idea if this was a licensing thing or what). It's an interesting gimmick to replace how Swapping out CDs worked for the original Playstation game, but most people use the Keyword generation in the North American version.
Thankfully, we solved how keywords worked. After scripting out auto-solving more than 2 million keywords, and filtering out duplicates, we have published options for every baseline, and every variant (stuff that has different stat gains, starting stats, starting techs, or faster guts regeneration from the baselines).
Keyword Solver for manual entry of any keywords you want, to see what it will produce
Curated list of Keywords: Pick a Kaiju main, then Kaiju sub. Below the choice will be a scrollable table of all the Script-found Kaiju and fan-submitted Kaiju
NTAG scanning and Bus Passes are solved too.
The bus passes are fun/interesting because the remaining balance of Yen on them is what determines what it makes. Many of the numbers are references to Ultraman or Monster Rancher lore. If you're curious about that, check out: https://legendcup.com/faq-ukmrnfc.php
I still prefer to think of it as magic. I hope they keep that appeal of 'i dno wtf gonna happen when I pop this in' from the original game in future games.
The remaster of MR1&2DX (Steam/Switch/iOS) does have a random button in addition to a searchable internal database of Albums, Song titles, and games.
For whatever reason, the Random button in Ultra Kaiju is absent from the North American version, so you just either have to enter in some random letters/words in the Keywords field, or use NFC. The Japanese and Southeast Asia versions of Ultra Kaiju have a CDDB and Random button, though the "CDDB" is a bit misleading because it actually uses the keywords lookup to generate the Kaiju from the CDDB entries. In this regard, at least, the North American version is superior since the Keywords aren't locked to a pre-defined list.
Why did JP and SEA get a Song List and NA got Keywords for UKMR? Maybe copyright or licensing, though it's honestly anyone's guess.
But it still would have been nice for them to keep the Random button :)
I started the Fan Site back in 1999, and even got Tecmo's blessing in writing, and I've also got IMDB/game credits in two of the games in the franchise from before the KoeiTecmo merger . It's been a hobby/obsession for over 2 decades that all started... mostly because My wife had beat the 1st game before me in '97, just waiting for me to get home from work to show me.
The Monster Rancher community is much smaller and overshadowed by other communities by comparison. MR's genre is pretty niche and hard to spread the word because of it, so I try :)
If you're referring to the Fandom wiki, that's an interesting topic of much debate, and I have nothing to do with it. It's got 1 or 2 main editors, but the real contention is the wiki attempts to link everything between every game plus the anime as a single cohesive piece of information, which ends up causing a lot of made up fan fiction just to connect the dots. The source material has been argued to be legitimate, but when pressed for the source, the wiki authors admitted that the data was from a Japanese cooking blog... which is never named, and no longer exists and cannot be found on any internet archive to cross reference
Additionally, the fandom wiki contains many completely made up monster lores and flavor texts from the Japanese translations that don't correlate. I did make an attempt to explain to the editors, using 1 particular monster as an example comparing the English text to the Japanese text. I provided the real translation and the likely meaning behind the name and lore description based on the direct translation of the name itself and the flavor text. This singular entry was changed, but none of the other hundreds (maybe thousands) of entries have been touched. Much of the guide information on the Fandom wiki is also out of date, or based on pre-data mining posts from the 90s/00s and not updated to the current findings that engineers and code hackers have discovered and published. If there's one thing the Fandom wiki has going for it, is that it has an impressive number of images across the many genres and platforms Monster Rancher has appeared on. I just wouldn't recommend trusting it for actual game information.
LegendCup isn't trying to connect everything to everything just for the sake of it, and doesn't acknowledge the Anime as a source of cannon for the games. Sort of like if you were to purchase a game guide about something, Each game's FAQs and guides are researched and dissected in isolation mechanically, and doesn't attempt to be a guide to the lore and history of monster rancher outside of providing references of actual in-game flavor texts of monsters within their respective games, along with data mined mechanics and information within each game.
Definitely, I plan to integrate spoilers with ActivityPub. For now, it's just a Markdown change compatible with Lemmy - there were many requests for it, and it was quite cumbersome. I will start working on federation after finish the refactoring. I want to do this on the new codebase - I'm getting closer, but initially, I'm fully focused on instance moderation, which will enable the operation of a global moderation team. Later, things with lower priority will be gradually implemented.
Are there any plans for the feed to always show new posts that you haven't seen yet, just like the reddit feed?
I mean, every time I open the "hot" section, for example, I see the same posts that are trending, even when I've already seen them before. It'd be nice to be able to see only content I didn't saw yet, so people will be always receiving new content and raising their interest and engagement :)
EDIT: I'm not complaining about the experience, just making a suggestion and I wanna thank you (as always) for your awesome work with /kbin! It's for sure my favorite social network!
Jokes aside, will this deployment process perhaps open up the possibility for beta testers? I think you've mentioned before that you have an experimental fork that you use for testing. I'd love to help out in that process.
Hey, I'll let you know when the test environments are fully ready. Currently, I'm using it more for reading logs of communication between instances. But I want to do it more thoroughly soon. Thanks!
kbin.social
Najstarsze