Spider

Yes would be interesting to see. The JSW 'engine' on that platform does not seem to suffer from the original flickering effect that upset MM and they do play quite well (imo) as standard, however there's usually room for adjustment and improvement. There's a few quirks copied over too , for instance Swimming Pool item is auto collected (at least in JSW1 , can't remember if it happens in full JSW2) for the only reason the ZX one is.

Yes, it seems that once the converter found something "it did not like too much" it simply truncated that post down, which it should not of done. It should of really just offered an option to carry on, stop or at least logged its actions. I can tell you it did not complain of -any- errors! To be fair the code is well written so quite how it managed to fall through I'm not completely sure. I agree I do not think this is as widespread as initially thought, its only likely to effect special characters, and then not all of them either. No-one was to know. Not your fault! 🙂 I'd agree with this, because the 'damage' as such was caused by the conversion tool, which was ran a long time ago. It should not of been knocked unconscious and truncated data when it seemed "did not know what to do" , its not something I can file as a bug now anyway given the previous version would not be supported. I found further evidence of this on Wikipieda too: I cannot (as best as I can) foresee any issues moving forwards as the table is fully UTF8MB4 ( see here ) so there should be sufficient "space" for most sane character encoding schemes. I do appreciate the concern however. To this end to eliminate worries, I've created a temporary topic in the 'testing forum' , please feel free to quote and copy/paste/type in non-standard characters, although I'd rather the topic does not span more than one page. In a few days I'll attempt to restore this on my own local server and provide a screenshot of its outcome.

Thoughts of making the JSW title screen contain two stacked 'triangles' spring to mind for a moment, then I could not deal with thinking about it! 😄

I thought about it. As best as I can tell (and I hate mysql charset concerns) , the issue was caused by mix encoding, that being that although most of the database was iirc ISO8859 , the checks appeared to fail during the conversion to UTF8MB4 as the tables themselves may of already "been there" , best way I can describe it sorry. Single (old) vs double(new) byte encoding per character in effect There's a few items about this kind of thing via Google, although the most relevant one seemed to be about a WordPress blog conversion, the user had a similar issue. The good news (as good as it can be) I would strongly suspect on this site that it is only going to effect posts that used what I'd call "non standard characters" so the actual 'missing content' is hopefully highly limited as not many members here use these. There are safety checks in the conversion routine however it seemed for reasons unknown to fail them. I can't post the code itself as its © , however I can post the comments in the relevant section that failed. Its quite likely this was updated in the core product some short time afterwards: I'd speculate here "nail/head" 🙂 The other good news really is as I'd performed the conversion well before the site's erm 'holiday' and then its restoration and upgrade on the newer host, there's no doubt as to when the problem happened. By this I mean there's no real question (as I can see it) of if it was an upgrade issue or a host issue or a conversion issue. It has to be the latter. Had I left the conversion until the upgrade it would of ran then anyway, potentially causing difficulty in (as we later found) discovering the likely root cause. So, summary all being well the damage -should- be relatively localised to said characters. 🙂

Absolutely zero harm @Richard Hallas , I'd rather hear something twice than not at all as someone thought it had been already said etc. 🙂 As above, with his permission we now host a copy of this excellent work, with a screenshot selection I made to go along with it and split read_me / tech_info details.

No problem. Yes it was very much well worth the time to do it, I've since found a slightly easier method of this now I've had chance to look into it in more detail too.

Good / Neutral / Bad etc: https://jswmm.co.uk/topic/532-jet-set-jason-in-rodd/?do=findComment&comment=13393 🙂

Topic (manually) recovered. Details of restored data. Good: I was able to restore six valuable posts. Neutral: They lost part of their formatting, this can be put right easily enough with simple edits Bad: There's no more data for this topic to restore, this -is it- as such. However I suspect what was removed or lost we can manage without. 🙂 jetsetdanny's post here is now fully populated jetsetdanny's post here was also restored, this was a very large post compared to what we had present korzy_iz_adb's post here restored, again this was a large post of useful content too jetsetdanny's post here restored, this also a large useful content post korzy_iz_adb's post here restored IRF's post here restored 🙂

I don't have the specifics to hand but I do remember when I altered one project, I had to fiddle about (read: experiment) with iirc two area's to make the air supply behave properly. My concern at the time was to get the 'lowest bar' into the right place.

Thanks for the continued updates! 🙂 🙂 🙂

😮

Not exactly 100% the same I know (not used JSON, normally XML or on rare occasions JS) although these things were a pain when they happened , the infamous javascript "alerts" popups. I've provided a suitable message given the forums theme:

Have added the screenshots (640x512 in jpg format) as a separate .zip file, just for those who wish to have their own copies of them to hand.

Thanks @jetsetdanny It looks 100% to me. I've just made a tiny alteration to the download page, although merely to put the 'detailed tech notes' from the descriptor into a text file rather than on the main page itself. Nothing else was changed. I thought that better as its allows an easier to read experience for those who want the basics of it without the detail, and the documented changes are in said text file for those who want to refer to it. 🙂

Thanks to @crem for creating us a new favicon. 🙂 I've applied it. Given browser differences it may take a bit of time to appear. I do recall (many years back) browsers especially elderly versions of I.Explorer etc were a bit difficult sometimes to persuade to pick up the new one, even after removal of temp data. Here's a quick pic for now anyway taken from a browser I don't tend to use much so it grabbed the new favicon:

Now (with TobyLobster's permission) also present here. 🙂

Regarding the above 'Entertainer' attached is a simple 2min (approx) mp3 of the above, although it erm plays a bit faster than normal, it does sound quite reasonable at a slightly "increased pace" though. entertainer_faster.mp3 🙂

Thank you @TobyLobster 🙂 I've submitted it here, set with you as 'submitter' so you are able to edit it if the need arises. I've done the following: Attributed it to yourself and D.Coathupe as 'third party' and 'original' authors respectively. Rather than just place the .ssd into the download , decided to make it a bit nicer for the end user by: Put the basic info into a 'read_me' text file Put the tech notes into a 'tech_notes' text file Taken screenshots of the title screen, all caverns and two of the game over screen Placed the above (aside from screenshots) into a zip and uploaded. You can find the download page here > https://jswmm.co.uk/files/file/145-manic-miner-2021/ Its support topic (auto generated) is here > https://jswmm.co.uk/topic/596-file-manic-miner-2021/ They both link to each other anyway, if by any chance you do edit it, please edit the download not the topic/thread as it will lose changes, editing the download updates the topic automatically. 🙂

Thank you! 🙂 Copy/Delete vary between emulators a bit! Plus iirc at least one of them allows both 'real' and 'logical' key mappings just to add to the confusion. 🙂

This is excellent, there's no other word for it. I was thinking would it be possible to perhaps host it here too in our download section (with some screenshots and a description) 🙂 We do have a few BBC variants of Manic Miner already here, standard and a couple of 'prepatched' cheat ones.

Thanks. :) The favicon I will admit I'd completetly forgotten about. I've uploaded a generic one for now, actually its the 3x version of this software's as the 4x does not have one. If memory serves at one point we just had a regular " smiling face " yellow smilie as the favicon. I do remember in dim/distant past trying to make something with M.W but given the size limitations of the favicon it proved difficult. There is some truth (apparently) in lower rankings for http vs https sites, I have heard that before. The reason it was not actually enabled (without boring you too much) as the host seemed to specify a huge array of htaccess code to go along with it, unfortunately this did not play nicely with the existing code we have in there and as at that moment in time it was a question of reopening the site asap, I felt it more important to "open the doors" after a few months being closed. Having said that I've just enabled it without their extra htaccess, so we'lll see if that is actually enough. In theory it ought to be, only possible concern perhaps is the browser complaining about mixed content but I think this may only happen where its a remote linked image, ie someone has not uploaded it but used the IMG tags instead.

Thanks for the updates! 🙂

Eugene hungry ? 🙂

I was used to seeing the # prefix and sometimes a 'h' suffix. Starting on the Spectrum platform in 84, there was not really any built in hex facility. Those who perhaps started coding on the Acorn machines may be more used to & however. For instance typing PRINT &C9 will return you with an answer of 201 , which is correct as #C9 is 201 in decimal. This is also accepted for the Amstrad CPC range too. Can't recall which but one emulator in the "insert pokes" section seems to prefer a $ prefix for hex values too, just to add to the mix! Personal preference is simply #xx as its quite easy to distinguish between: LD A , #80 JP #7530 Decimal of the above: LD A , 128 JP 30000 I do realise I'm slightly contradicting myself as today I did provide some 'pokes' using a different prefix however the prefix suited the platform they were intended for! , but in general if I was writing a post or such I'd rather just use #value, its easy to type and does not or should not lead to any confusion.

I mean to say utf8mb4 Pre conversion (some tables were already at this) , it only effected display. The parser would not be knocked unconscious by broken bbcode, I do know what you're referring to though. 🙂 I did get the data when I did the restore from the raw database via phpmyadmin directly 😉 Upon closer examination of a backup directly, the UTF8MB4 conversion appeared to have done this. Unfortunately had I delayed this, it would of happened anyway at the 3x to 4x upgrade. EDIT... Updated, read end of post info! Looking at post 11772 for instance here , I find the 'converted' (but pre-upgrade backup from last year) was truncated: 3x data (converted) 3x data (pre conversion) Unfortunately, as noted the conversion was not a recent thing, not even near the upgrade at least as I remember. 4x looks like this (just an empty post saying "test" really) I am able it seems to 'rescue' some posts, having found a pre-conversion example, despite having said otherwise previously. No guarantee's on this however i have just restored this post , with only a minor cleanup needed.