[X] My Assistant

Hello everyone.

First and foremost, I am in charge of the operating and maintenance of the HentaiVerse player-side database, after taking over from Jenga a few months ago. A big thank you for all his work so far.

Now, what is the HV database? It is a service of public purpose that collects data with a SQL server and then allows everyone to make use of the said data, with the help of various APIs and tools. Currently, the database holds data for equipments, monsters and miscellaneous drops, but we may expand that in the future if the need arises, and if I have enough time too.

Keep in mind that because the operating and maintenance of the database and its tools require a lot of server resources and a lot of time, I may not be able to solve all issues in a snap. So when issues arise, be patient and try to make my job easier by gathering all the relevant elements / information.

1) The equipment database
The equipment database stores all the data associated to the equipments that have been registered in it: equipment is, key, name and all its stats. As of today, it is used by the Live Percentile Ranges script to refresh the Min/Max of each range. It is supposed to be used to update the wiki ranges too, but as of today skillchip is away from HV. Until the current equipment range issues are solved, getting that to be done again is on standby.

Do believe that I'm doing my best to get these range issues to be solved, and hopefully everything will be solved soon.

How to feed the equipment database
Simply add the following script to your Tampermonkey in Chrome/Firefox, and you don't even need to think about it.

CODE

// ==UserScript==
// @name           HV - Items
// @namespace      hvitems
// @version        2.1
// @description    Registers equipment in the equipment database
// @author         Jenga, decondelite
// @grant          none
// @match          *://*.hentaiverse.org/?s=Bazaar&ss=es*
// @match          *://*.hentaiverse.org/?s=Character&ss=in*
// @match          *://*.hentaiverse.org/?s=Forge&ss=sa*
// @match          *://*.hentaiverse.org/?s=Bazaar&ss=fr*
// ==/UserScript==

var equipment = [];
for(var eid in dynjs_equip) {
    // Skips equipment before v0.83 (bugged power was during v0.82)
    if (eid<74306995) continue;
    equipment.push({"eid":eid, "key":dynjs_equip[eid].k});
}

if(equipment.length > 0){
  var httpReq = new XMLHttpRequest();
  var data = new FormData();
  data.append('action', 'store');
  data.append('equipment', JSON.stringify(equipment));
  httpReq.open("POST","https://hvitems.niblseed.com/");
  httpReq.send( data );
}

2) The monster database
The monster database stores all the monster data. It is used by the Monsterbation script to display that data during battles. You can also query the database with the use of [hvlist.niblseed.com] the monster search web page.

Please be aware that because the database is used for public purposes and because you probably appreciate seeing your own monsters appearing in it, it is everyone's duty to keep the monster database up to date by scanning them during battles (while using the Monsterbation script). If you intend to use the database without feeding it yourself, well... shame on you.


3) The loot database
It is currently unused, but it used to collect data to then build stats with it. It will be used again once everything else is fixed.


Current status
HV API (monster database) - OFFLINE
hvitems (equipment database) - OFFLINE

This post has been edited by decondelite: Jan 4 2021, 00:36

Thank you. Let's see if it updates values...


Feature request:
Equipment database search page >_>

Based on the post by sssss2, the fix was done on August 10 2015, not on July 26 2015. 74306995 is very close to the reported equips from that date in the legendary equipment thread. And because it is peerless power, we know for sure that it was after the fix. Let's go with that.

I edited the script in the first post. You might want to check the DB for equips between what 7311etc and 74306995?

There is no solid evidence about that change being done on that date, but fine.
A higher eid won't do any harm.

We are facing SSL certificate issues along with an apache server that decided to be a prick tonight.
Unfortunately, I don't have time to deal with it this weekend, so expect a fix a bit later. I've only and barely had time to do some very basic fixes so the apache server is back up, though in a not fully operational state.
As a result, the monster database is unavailable. The equipment registration should be working right now, since it doesn't depend on an Tomcat server with a special certificate.

I'll keep you updated as soon as I have news.

After a lot of struggling, all issues are now solved. Everything is back to being 100% functional. (IMG:[invalid] style_emoticons/default/smile.gif)
There should be lots of monsters to update now.

This post has been edited by decondelite: Mar 19 2019, 23:03

Due to the recent heavy load, the HV API stopped working, and this time it utterly refuses to recover.
I'm afraid that the database won't be able to provide monster data before I just code a brand new API. The current one is badly optimized and puts too much of a strain on the server.

You still can scan monsters to feed the database, and query the monster page.

I will update whenever I have news.

is scanning working at the moment? There are no monsters scanned in the last 30 days!

I asked randomuser to add a code to add scans to the database. I'll then modify the code if necessary, to take care of the possible extra security checks or God knows what. I completely forgot that in the bounty, and the scans are very, very likely to be the one thing that pops the errors in the API's console. I can't believe that such a thing went past my checks.

So right now, all scanning does is updating your local Monsterbation cache. Still better than nothing I guess. I'll keep everyone updated.

Scanning works now. (IMG:[invalid] style_emoticons/default/smile.gif)

Small heads up.

The ownership of the niblseed.com domain is being transferred from Jenga to me. During this process, the various URLs used by the services are unable to respond. This may take a few days, so please bear with us. (IMG:[invalid] style_emoticons/default/smile.gif)

Hey guys,

I've been like really out of touch lately and for quite a while.
I still love you all though.

Is the monster database working, or is it just my own code setup?
I am not seeing the data to the right of the monsters during play.

If it's not working at present, I'm not sweating it.
Coding is a pain in the ass, and is outrageously time consuming.
So... I'm not trying to go down that road of "are we there yet!?! are we there yet!?!

I just want to assure the concern is not on my side.

Thank decondelite and thanks to all. (IMG:[invalid] style_emoticons/default/smile.gif)

Hey guys,

I've been like really out of touch lately and for quite a while.
I still love you all though.

Is the monster database working, or is it just my own code setup?
I am not seeing the data to the right of the monsters during play.

If it's not working at present, I'm not sweating it.
Coding is a pain in the ass, and is outrageously time consuming.
So... I'm not trying to go down that road of "are we there yet!?! are we there yet!?!

I just want to assure the concern is not on my side.

Thank decondelite and thanks to all. (IMG:[invalid] style_emoticons/default/smile.gif)

oh, right - I think you need to update HV utils and Monsterbation for the monster DB functions to work again!

thanks for your job

The equipment database is currently undergoing a reorganisation of its internal structure.
There won't be any data loss (mostly written in a different way), but the scripts that are using the database will simply stop working.

I don't have any ETA about when this will be over: it depends on the amount of free time I have on my hands.

The equipment database is currently undergoing a reorganisation of its internal structure.
There won't be any data loss (mostly written in a different way), but the scripts that are using the database will simply stop working.

I don't have any ETA about when this will be over: it depends on the amount of free time I have on my hands.

Hope everything goes smoothly
Also, just wanted to say thank you as someone who uses it

The equipment database is currently undergoing a reorganisation of its internal structure.
There won't be any data loss (mostly written in a different way), but the scripts that are using the database will simply stop working.

I don't have any ETA about when this will be over: it depends on the amount of free time I have on my hands.

Only equipments, not monsters, right?

On Feb 1 I encountered my monster and failed to update it no matter how much times, different browsers, wifi and such, I used.

On Feb 3 I succeeded first try.

On Feb 7 I couldn't do it again (IMG:[invalid] style_emoticons/default/duck.gif)

The database optimization and cleanup is finally done.
It is now taking up roughly twice less disk space, is blazingly fast, and has a sturdy conception to guarantee the integrity.
To obtain a range:
-Before; ~20-30 minutes
-Now: ~10 seconds

Now we need to start feeding it again. I will make a crowdfunding thread to upgrade the HV API soon.

Not sure I should post here, but I got a problem linked to the Monster Database and Monsterbation Script, and since nobody else reported it yet, it may be on my end only.

It's been a few days that monster data from the DB doesn't show up in battle anymore, even if I scan them myself. Thing is, it happened suddenly during an Arena run, Sunday evening (for me).
At first, I thought I messed up some Monsterbation settings 'cause I added hotkeys to one of my profiles during a round, exited the Settings menu and then the data stopped appearing. But resetting Monsterbation and even re-installing the script changed nothing.

So I tried to access [hvlist.niblseed.com] https://hvlist.niblseed.com/, see if it's still on or if my scans were counted, but my browsers show a warning message: "This Connection is Untrusted", and under technical details: "hvlist.niblseed.com uses an invalid security certificate. The certificate expired on Sunday August 23 2020 22:31. The current time is Tuesday August 25 2020 18:50. (Error code: SEC_ERROR_EXPIRED_CERTIFICATE)"
Tried with Palemoon (browser default warning message), Firefox and Chrome (for these 2, message is from my AV, Kaspersky Security Cloud Free).

I don't quite understand what's going on, since it seems I'm the only one affected. Does anyone have more clue?

edit: just done a RE, problem is fixed, and the DB site is accessible again (IMG:[invalid] style_emoticons/default/smile.gif)
Thanks for the quick fix!

This post has been edited by Venvalion: Aug 25 2020, 20:30

Deleted a few useless tables in the monster database and cleaned the PHP code that comes with it.