Nitro x Plus Emulator.
- Thread starter pau
- Start date
- Thread starter
- #4
How would that be?
Post automatically merged:
The problem is that the hotel has 2 years and it has registered users, ...
Last edited by a moderator:
airilxx
Member
- Jan 1, 2012
- 51
- 12
With a simple google search, you can easily find matching packets that's compatible with Plus EMU to be used with Nitro. S
Server Header :
Client Header :
Here is one of the PlusEMU with built-in Netty, so you only need to change packets and you're ready to go!
Server Header :
You must be registered for see links
Client Header :
You must be registered for see links
Here is one of the PlusEMU with built-in Netty, so you only need to change packets and you're ready to go!
You must be registered for see links
Last edited:
Solid
Active Member
- May 1, 2012
- 126
- 31
With a simple google search, you can easily find matching packets that's compatible with Plus EMU to be used with Nitro. S
Server Header :You must be registered for see links
Client Header :You must be registered for see links
Here is one of the PlusEMU with built-in Netty, so you only need to change packets and you're ready to go!
You must be registered for see links
You must be registered for see links
lol
Morohara
Member
- May 18, 2020
- 92
- 55
The warnings that you've posted are easily fixed.
Try posting the correct tab if you require help. also try not to just willy nilly copy and paste without reading the code to avoid errors.
Those warnings can be fixed by adding the namespaces at the top of your file simply type at the top of the file using system.linq. you want it to look like this
You must be registered for see links
.Thought I'd do something abit more helpful down the line for you as well
You must be registered for see links
. At the top of the file you'll see "string Devbest = "hello";then at the bottom you'll see Console.WriteLine(devbest); The reason for the errors is because the d in the second line isn't called correctly and the string "devbest" doesn't exist. This can result in errors which I'm going to suspect are will probably be "assembly reference missing blah blah blah" normally clicking the error and clicking the lightbulb on the left next to the line number will provide a fix but normally a character error.
Last edited:
airilxx
Member
- Jan 1, 2012
- 51
- 12
Its a simple fix actually. Reinstall those required .dll packages from NuGet Package Manager, and then you'll need to comment those unexist packets.
Solid
Active Member
- May 1, 2012
- 126
- 31
thanx, what about this ?
You must be registered for see links
Solid
Active Member
- May 1, 2012
- 126
- 31
Comment this
You must be registered for see links
Added but still error.IF this helps here:
Packetmanager.cs:
You must be registered for see links
ServerPacketHeader.cs:
You must be registered for see links
Last edited:
Morohara
Member
- May 18, 2020
- 92
- 55
Edit changed what i said delete line 225 and rebuild the solution. This error could have been fixed on you're own. If you look at
public void RegisterNames()
{
_packetNames.Add(ClientPacketHeader.GetClientVersionMessageEvent, "GetClientVersionEvent");
_packetNames.Add(ClientPacketHeader.InitCryptoMessageEvent, "InitCryptoEvent");
_packetNames.Add(ClientPacketHeader.GenerateSecretKeyMessageEvent, "GenerateSecretKeyEvent");
It's calling for public const int InitCryptoMessageComposer = 1347; // PRODUCTION-201611291003-338511768 twice and shouldn't be. It states that in the first error.
public void RegisterNames()
{
_packetNames.Add(ClientPacketHeader.GetClientVersionMessageEvent, "GetClientVersionEvent");
_packetNames.Add(ClientPacketHeader.InitCryptoMessageEvent, "InitCryptoEvent");
_packetNames.Add(ClientPacketHeader.GenerateSecretKeyMessageEvent, "GenerateSecretKeyEvent");
It's calling for public const int InitCryptoMessageComposer = 1347; // PRODUCTION-201611291003-338511768 twice and shouldn't be. It states that in the first error.
Last edited:
Solid
Active Member
- May 1, 2012
- 126
- 31
error after removing line 225 and rebuilt:
You must be registered for see links
Solid
Active Member
- May 1, 2012
- 126
- 31
Packetmanager.cs:
You must be registered for see links
ServerPacketHeader.cs:
You must be registered for see links
Morohara
Member
- May 18, 2020
- 92
- 55
His post was confusing and if you check some of the packet ids they conflict as using the same ID.
Copy and paste this
You must be registered for see links
back into the file. The error posted was one of the packets was using 4000 twice and that isn't good. also do go to the line 225 in packetmanager.cs and delete that as that will also cause an error. (ONLY do this if line 223 & 225 are the same. _packetNames.Add(ClientPacketHeader.InitCryptoMessageEvent, "InitCryptoEvent"); )
Last edited:
