Mercury Emulator V2.3 [Plus] [New RSA] [Love Locks] [Group Forums] [ETC]

[KyleeIsProzZ]

I wouldn't use this emulator before fixing the security holes in it...

This has no major security holes or exploits. Not that I know of anyway. Just needs to be cleaned up like the code and make the code more secure, which is not hard to change the code into. But will take effort and time, And will make you bored. But if you have patience, then do so. This is the best emulator so far then the history of this section. I bet you joined a hotel for like 2 minutes then just putting "It has got security holes" without actually looking at the source and speculating. This is just an answer to you, not to start a war against me for putting this. If you have different visions, opinions and sightings of these such "Security holes.". please point them out and post what they do before flaming a release topic with such bs.

[smatch]

It's you, i don't have that problem

It's why on your server, all normal user is rank> 1.
On my server, everyone is rank 3 (VIP).
Anyone VIP user can join the rooms.
I need to know where to change it in the source.

[Jonteh]

And yet here you are, using his work for free... What a hypocrite!

If you can fix this holes/exploits/clean it up/etc... Then do it, but don't bash this guy's work, specially when you're using his work.

Yes, we are using this for free. And I have fixed it, cleaned it up, and patched exploits. I never said the Emulator was shit, just that he rushed it.

Not hypocritical at all, just a comment from a fellow developers point of view - he could of taken more time and care, that's all.

- - - Updated - - -

No security holes, no exploits, just need to clean up the code and make the code more secure, which is not hard to change the code into. But will take effort and time, And will make you bored. But if you have patience, then do so. This is the best emulator so far, I bet you joined a hotel for like 2 minutes then just putting it has security holes without actually looking at the source. This is just an answer to you, not to start a war against me for putting this. PM me if you have different visions, opinions and sightings of these such "Security holes.". Before flaming a release topic with bs.

It does have security holes, because I have fixed 2 so far, and used them on other hotels myself.

[Eduarpack]

I know you didn't say it was shit, neither did i (maybe you subconsciously thought it was shit). I think nobody cares if you fixed it or not, or at least i don't.

Your ''developer's point of view'' was fine until you ended it with this:

Prepared statements guys, when will you learn

. It really made you look like an ass when i read that.

[Diddy]

There is a security hole.
A user called AWA added himself to ownership.

No one made him it.

I was told by johno this is a exploit in the emu.

[Jonteh]

I know you didn't say it was shit, neither did i (maybe you subconsciously thought it was shit). I think nobody cares if you fixed it or not, or at least i don't.

Your ''developer's point of view'' was fine until you ended it with this: . It really made you look like an ass when i read that.

I am an ass, but at least I'm honest.

- - - Updated - - -

There is a security hole.
A user called AWA added himself to ownership.

No one made him it.

I was told by johno this is a exploit in the emu.

This exploit is one I've fixed, I posted the cause in an earlier post, but you can fix it by changing the runFastQuery to:

queryreactor3.setQuery("UPDATE bots SET automatic_chat = @autochat, speaking_interval = @interval, mix_phrases = @mix_phrases WHERE id = @botid");


queryreactor3.addParameter("autochat", text2);
queryreactor3.addParameter("interval", Convert.ToInt32(value));
queryreactor3.addParameter("mix_phrases", text3);
queryreactor3.addParameter("botid", num);
queryreactor3.runQuery();

[scullyuk]

Hey Guys.
Was just wondering if you know anything about this error on mercury?

It seems that when all users leave a room it somehow 'locks' everyone out. When I go inside the room, everything loads like the room and furni, but i cant walk in and the room name just shows ...

Chat also doesnt work.

But each time I load these rooms this is the error the emu gives:
Error en thread Room cycle task for room 41:
System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.ValueCollection.Enumerator.MoveNext()
at Mercury.HabboHotel.Rooms.RoomUserManager.OnCycle(Int32& idleCount) in c:\Users\Jake\Downloads\MercuryNew\HabboHotel\Rooms\RoomUserManager.cs:line 1293
at Mercury.HabboHotel.Rooms.Room.ProcessRoom() in c:\Users\Jake\Downloads\MercuryNew\HabboHotel\Rooms\Room.cs:line 756

I have looked all around the forums but nobody seems to be fixing this error, but a lot of people are getting it.

I would be very greatful if anybody can help me with this.

Thanks,
Ben

[MrPudding]

I am an ass, but at least I'm honest.

- - - Updated - - -



This exploit is one I've fixed, I posted the cause in an earlier post, but you can fix it by changing the runFastQuery to:

queryreactor3.setQuery("UPDATE bots SET automatic_chat = @autochat, speaking_interval = @interval, mix_phrases = @mix_phrases WHERE id = @botid");


queryreactor3.addParameter("autochat", text2);
queryreactor3.addParameter("interval", Convert.ToInt32(value));
queryreactor3.addParameter("mix_phrases", text3);
queryreactor3.addParameter("botid", num);
queryreactor3.runQuery();

Many thanks for your contribution! :)
It's a good step in Mercury's development :P

[Eduarpack]

I am an ass, but at least I'm honest.

You do know you can be honest without sounding like a hypocrite, right?

But whatever, this is going nowhere so let's move on.

[akajsmoove]

Don't know if anyone had this issue, but furniture in rooms breaks sometimes, you're able to walk on the furniture and when you reload the room the furniture isn't there but in your hand?

[AWA]

I am an ass, but at least I'm honest.

- - - Updated - - -



This exploit is one I've fixed, I posted the cause in an earlier post, but you can fix it by changing the runFastQuery to:

queryreactor3.setQuery("UPDATE bots SET automatic_chat = @autochat, speaking_interval = @interval, mix_phrases = @mix_phrases WHERE id = @botid");


queryreactor3.addParameter("autochat", text2);
queryreactor3.addParameter("interval", Convert.ToInt32(value));
queryreactor3.addParameter("mix_phrases", text3);
queryreactor3.addParameter("botid", num);
queryreactor3.runQuery();

GJ on the fix! The original was both unparamized and decompiled code, real quality!

[Jonteh]

GJ on the fix! The original was both unparamized and decompiled code, real quality!

Prime example of why I hate using Plus Emulator and it's edits - however I was pushed to it by the hotels I develop for as my Butterfly R63B was "taking too long".

[TardisHotel]

And yet here you are, using his work for free... What a hypocrite!

If you can fix this holes/exploits/clean it up/etc... Then do it, but don't bash this guy's work, specially when you're using his work.

1. He never bashed this guys work he had to fix the exploit as Tardis was exploited and we found out the hard way it had this exploit
2. Jonteh was posting the fix so no one else went through this
3. stop sitting on rz going on at peoples posts like this when all he was doing was helping and pointing out A FACT
4. The rest of you should run the fix like NOW so this doesn't happen to you.

[smatch]

Hi ;-)

Image of group in profile of user, not appears.
How to fix it?


Thanks brothers!

[Eduarpack]

1. He never bashed this guys work he had to fix the exploit as Tardis was exploited and we found out the hard way it had this exploit
2. Jonteh was posting the fix so no one else went through this
3. stop sitting on rz going on at peoples posts like this when all he was doing was helping and pointing out A FACT
4. The rest of you should run the fix like NOW so this doesn't happen to you.

I'm not sure what you're trying to achieve with this, but we already discussed and moved on.