Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error with x y itemappeared #3273

Closed
notekubpom opened this issue Sep 24, 2020 · 11 comments · Fixed by #3282
Closed

error with x y itemappeared #3273

notekubpom opened this issue Sep 24, 2020 · 11 comments · Fixed by #3282

Comments

@notekubpom
Copy link

------------------ Openkore Issues Template ------------------

  • Openkore version git:
  • Server:
  • Bug Report / Feature Request:
  • Summary:

my bot not pickup the item
it a private server
no gepard
the item show wrong x y in console
Untitled (1)

the client date: 20200302 form bpe-master
my server.txt
[rofi-ro]
ip 103.91.207.20
port 6900
private 1
version 47
master_version 103
serverType kRO_RagexeRE_2018_11_21
recvpackets recvpackets.txt
serverEncoding Western
charBlockSize 155
addTableFolders translated/kRO_english;kRO

this is my recvpackets.txt
recvpackets.txt

@ya4ept
Copy link
Contributor

ya4ept commented Sep 24, 2020

received a link to the client and test account

@notekubpom
Copy link
Author

received a link to the client and test account

full data
https://drive.google.com/file/d/1vfNy5vvUoJ_QT6We9qqVTpIVInGF799K/view?usp=sharing
only exe
https://drive.google.com/file/d/17srGTlGrIXGJIJEBjHSArJTNskUXNrap/view?usp=sharing
username : testacc
password : note1234

@alisonrag
Copy link
Contributor

if using 2018+ servertype, there is no support to new item system yet
all items changed the nameID length in packets

@notekubpom
Copy link
Author

anyway to fix it bro.

@alisonrag
Copy link
Contributor

Always have a way to fix it :)
Just need to update src and update item lenght
Maybe ya4ept will do this

@notekubpom
Copy link
Author

ok need to update

@ya4ept
Copy link
Contributor

ya4ept commented Sep 26, 2020

I don't understand why we need to send packet '0ACF'
after that the client still sends a regular packet '0064'
The server accepts the bot, even if we immediately send the packet '0064'

изображение

@sctnightcore
Copy link
Member

sctnightcore commented Sep 27, 2020

@ya4ept I will only update this packet when hacktoberfest activity. Starting next month

0ACF
struct PACKET_CA_LOGIN_OTP {
	int16 packet_id;      ///< Packet ID (#HEADER_CA_LOGIN_OTP)
#if PACKETVER >= 20171113
	uint32 devFlags;      ///< flags including dev flag
#endif
	char login[25];       ///< Username
	char password[32];    ///< Password encrypted by rijndael
	char flagsStr[5];     ///< Unknown flags. Normally string: G000
} __attribute__((packed));

0AE3
struct PACKET_AC_LOGIN_OTP {
	int16 packet_id;
	int16 packet_len;
	int32 loginFlag;
	char loginFlag2[20];
	char token[];
} __attribute__((packed));
DEFINE_PACKET_HEADER(AC_LOGIN_OTP, 0x0ae3);

@ya4ept
Copy link
Contributor

ya4ept commented Sep 30, 2020

@note the server died?

@notekubpom
Copy link
Author

@ya4ept yes server already died

@sctnightcore
Copy link
Member

image
@notekubpom

just update only 0ADD . :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants