Time to clean out my old submissions that never got added to the updates for whatever reason.
Reg hive: HKEY_CURRENT_USER
Reg Path: Software\Encore\IGT® Slots Paradise Garden™
Backup entire key: Yes
IGT Slots Paradise Garden
- InsaneMatt
- Site Admin
- Posts: 478
- Joined: 22 Jan 2018, 00:33
Re: IGT Slots Paradise Garden
The registry key path seems malformed, could you confirm it?
If needed, a picture of it's path in Registry Editor would do.
If needed, a picture of it's path in Registry Editor would do.
Re: IGT Slots Paradise Garden
Sorry for the late reply.InsaneMatt wrote: ↑29 Jul 2018, 18:36 The registry key path seems malformed, could you confirm it?
If needed, a picture of it's path in Registry Editor would do.
I can confirm it looks like this.
here's a screen shot
![Image](https://i.imgur.com/gLm7dTN.jpg)
- InsaneMatt
- Site Admin
- Posts: 478
- Joined: 22 Jan 2018, 00:33
Re: IGT Slots Paradise Garden
Very unusual string there, but whatever.
Database Update released.
Database Update released.
Re: IGT Slots Paradise Garden
Error found in the update.InsaneMatt wrote: ↑06 Aug 2018, 12:44 Very unusual string there, but whatever.
Database Update released.
Reg path in the update:
Code: Select all
HKEY_CURRENT_USER\Software\Encore\IGT® Slots Paradise Garden???
Code: Select all
HKEY_CURRENT_USER\Software\Encore\IGT® Slots Paradise Garden™
- InsaneMatt
- Site Admin
- Posts: 478
- Joined: 22 Jan 2018, 00:33
Re: IGT Slots Paradise Garden
Try re-downloading the update.
Appears there's an issue with how the v3.x branch compiles the database, which I've addressed by manually modifying the entry.
---
EDIT: Appears the characters used just cannot be stored in the v3.x database, but appears fine in my tests in v4.x
Very odd.
Appears there's an issue with how the v3.x branch compiles the database, which I've addressed by manually modifying the entry.
---
EDIT: Appears the characters used just cannot be stored in the v3.x database, but appears fine in my tests in v4.x
Very odd.
Re: IGT Slots Paradise Garden
Odd indeed.InsaneMatt wrote: ↑06 Aug 2018, 22:01 Try re-downloading the update.
Appears there's an issue with how the v3.x branch compiles the database, which I've addressed by manually modifying the entry.
---
EDIT: Appears the characters used just cannot be stored in the v3.x database, but appears fine in my tests in v4.x
Very odd.
I assume custom entries are stored differently than the official V3.x database, since the custom entry works fine.
Who is online
Users browsing this forum: No registered users and 0 guests