Thread: Creating outgoing packets

Page 1 of 2 12 LastLast
Results 1 to 10 of 11
  1. #1 Creating outgoing packets 
    Banned
    Join Date
    Jul 2015
    Posts
    126
    Thanks given
    21
    Thanks received
    9
    Rep Power
    0
    So I'm trying to create an outgoing packet for the login screen.

    I have this.

    Code:
    	public void showWelcomeScreen(int days, int unreadMessages, int member, int ip) {
    		c.outStream.createFrame(176);
    		c.outStream.writeByteC(days);
    		c.outStream.writeWordA(unreadMessages);
    		c.outStream.writeByte(member);
    		c.outStream.writeDWord_v1(ip); //These methods are from a PI. (I realize how shitty they are)
    	}
    Here's the packet client-sided

    Code:
    			case PacketID.OPEN_WELCOME_SCREEN: //176
    				daysSinceRecovChange = inStream.method427();
    				unreadMessages = inStream.method435();
    				membersInt = inStream.readUnsignedByte();
    				playerIpAddress = inStream.method440();
    				daysSinceLastLogin = inStream.readUnsignedWord();
    				if (playerIpAddress != 0 && openInterfaceID == -1) {
    					Signlink.dnslookup(TextClass.method586(playerIpAddress));
    					clearTopInterfaces();
    					char c = '\u028A';
    					if (daysSinceRecovChange != 201 || membersInt == 1)
    						c = '\u028F';
    					reportAbuseInput = "";
    					canMute = false;
    					for (int k9 = 0; k9 < RSInterface.interfaceCache.length; k9++) {
    						if (RSInterface.interfaceCache[k9] == null || RSInterface.interfaceCache[k9].contentType != c)
    							continue;
    						openInterfaceID = RSInterface.interfaceCache[k9].parentID;
    
    					}
    				}
    				pktType = -1;
    				return true; // This enables the packet
    By looking at it, this is what I gathered.

    Code:
    176 - Show welcome Screen
    Days since recovery questions changed - ByteC
    Unread messages - ShortA
    Player is member - Byte
    Player ip address - Int1
    Any help would be much appreciated.
    Reply With Quote  
     

  2. #2  
    Author of the first public OSRSPS

    Shadowy's Avatar
    Join Date
    Sep 2009
    Age
    28
    Posts
    1,499
    Thanks given
    490
    Thanks received
    241
    Rep Power
    307
    whats the problem then

    and i cound 5 read methods in the client
    daysSinceRecovChange = inStream.method427();
    unreadMessages = inStream.method435();
    membersInt = inStream.readUnsignedByte();
    playerIpAddress = inStream.method440();
    daysSinceLastLogin = inStream.readUnsignedWord();

    ur sending 4
    Owner of OS-RSPS, the first Oldschool RuneScape Server (2014)
    Reply With Quote  
     

  3. #3  
    Banned
    Join Date
    Jul 2015
    Posts
    126
    Thanks given
    21
    Thanks received
    9
    Rep Power
    0
    Quote Originally Posted by Shadowy View Post
    whats the problem then

    and i cound 5 read methods in the client
    daysSinceRecovChange = inStream.method427();
    unreadMessages = inStream.method435();
    membersInt = inStream.readUnsignedByte();
    playerIpAddress = inStream.method440();
    daysSinceLastLogin = inStream.readUnsignedWord();

    ur sending 4
    Yeah I got it now, but how do I send the main interface? If I set the interface server-sided it doesn't become fullscreen. If I set it client-sided it is.
    Reply With Quote  
     

  4. #4  
    anInt69

    Max _'s Avatar
    Join Date
    Feb 2012
    Age
    26
    Posts
    1,801
    Thanks given
    426
    Thanks received
    727
    Rep Power
    599
    Quote Originally Posted by Rust View Post
    Yeah I got it now, but how do I send the main interface? If I set the interface server-sided it doesn't become fullscreen. If I set it client-sided it is.
    In the packet that receives the interface opening requests, check if that interface is supposed to be fullscreen or not.
    AFAIK the variable for openInterfaces and open fullscreen interfaces aren't the same.
    Reply With Quote  
     

  5. #5  
    Member Creating outgoing packets Market Banned


    Luke132's Avatar
    Join Date
    Dec 2007
    Age
    35
    Posts
    12,574
    Thanks given
    199
    Thanks received
    7,106
    Rep Power
    5000
    Quote Originally Posted by Rust View Post
    Yeah I got it now, but how do I send the main interface? If I set the interface server-sided it doesn't become fullscreen. If I set it client-sided it is.
    Only the real 377 client and above can display full screen interfaces, you're using a 317

    Attached imageAttached image
    Reply With Quote  
     

  6. #6  
    Banned
    Join Date
    Jul 2015
    Posts
    126
    Thanks given
    21
    Thanks received
    9
    Rep Power
    0
    Quote Originally Posted by Max _ View Post
    In the packet that receives the interface opening requests, check if that interface is supposed to be fullscreen or not.
    AFAIK the variable for openInterfaces and open fullscreen interfaces aren't the same.
    Alright thanks I'll check.

    Quote Originally Posted by Luke132 View Post
    Only the real 377 client and above can display full screen interfaces, you're using a 317
    Really? So there was no welcome screen in a 317, or how did they do it then?
    Reply With Quote  
     

  7. #7  
    Member Creating outgoing packets Market Banned


    Luke132's Avatar
    Join Date
    Dec 2007
    Age
    35
    Posts
    12,574
    Thanks given
    199
    Thanks received
    7,106
    Rep Power
    5000
    Quote Originally Posted by Rust View Post
    Really? So there was no welcome screen in a 317, or how did they do it then?
    Yes really, they added the login screen somewhere between 317 and 377 and a new interface 'type' (8), that your client doesn't know how to display

    Attached imageAttached image
    Reply With Quote  
     

  8. #8  
    Registered Member
    Join Date
    Dec 2011
    Posts
    793
    Thanks given
    204
    Thanks received
    176
    Rep Power
    173
    Quote Originally Posted by Rust View Post
    Alright thanks I'll check.



    Really? So there was no welcome screen in a 317, or how did they do it then?


    This was how it was done up until 377.
    Reply With Quote  
     

  9. #9  
    Banned
    Join Date
    Jul 2015
    Posts
    126
    Thanks given
    21
    Thanks received
    9
    Rep Power
    0
    Quote Originally Posted by Luke132 View Post
    Yes really, they added the login screen somewhere between 317 and 377 and a new interface 'type' (8), that your client doesn't know how to display
    Quote Originally Posted by Psychotic View Post


    This was how it was done up until 377.
    Ahh okay, thanks for the info guys. I got it working, just missing all the sendFrame126 ids for all the slots.
    Reply With Quote  
     

  10. #10  
    Registered Member
    natsu's Avatar
    Join Date
    Apr 2007
    Age
    32
    Posts
    3,435
    Thanks given
    1,084
    Thanks received
    676
    Rep Power
    1096
    Quote Originally Posted by Rust View Post
    Ahh okay, thanks for the info guys. I got it working, just missing all the sendFrame126 ids for all the slots.
    you got also do stewie's tutorial to support full screen interface's
    Reply With Quote  
     

Page 1 of 2 12 LastLast

Thread Information
Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)


User Tag List

Similar Threads

  1. Outgoing packets in client
    By Nemmyz in forum Help
    Replies: 0
    Last Post: 11-16-2011, 09:45 AM
  2. 317 Incoming and Outgoing Packets
    By Leanbow in forum Informative Threads
    Replies: 5
    Last Post: 07-26-2011, 01:52 PM
  3. Outgoing Packets.
    By The Almost in forum Help
    Replies: 9
    Last Post: 12-20-2009, 01:36 AM
  4. Replies: 3
    Last Post: 03-16-2009, 02:57 AM
  5. [525] Outgoing packets
    By Kelvin in forum Snippets
    Replies: 1
    Last Post: 02-23-2009, 08:27 AM
Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •