718 Few errors on the client (Clientscript.java & Class291.java etc..)

[Houssy997]

Hey everyone,I’m currently working on my own RSPS project based on Entrinthy 718/742 Enth release.
Both the server and client are using subrevision 3, and the server starts without issues.


However, the client crashes immediately with an opcode-related error.

What’s working : ​

Server compiles and runs fine (no console errors), Client compiles and launches, CUSTOM_CLIENT_BUILD (server) and SUB_REVISION (client) are both set to 3 , Cache directory is correctly referenced and contains: main_file_cache.dat2 , main_file_cache.idx0 through .idx25 Etc...

The problem : Client crashes with :​

Invalid opcode: 29184at Class346.method4175(Class346.java:165)at ClientScript.method3475(ClientScript.java:109)at ...

What I’ve already checked:​

Cache is complete (no missing or 0-byte files)

IP is set to 127.0.0.1, port is 43594 (matches the server)

Using a 718/742 Enth client, not modified (except SUB_REVISION)

Suspicions:​

Cache might be corrupt or not compatible with the client script decoder, ClientScript decoder may not match the cache’s script format

Looking for:​

A working 718/742 Enth client + cache setup for subrevision 3 Or a fix for the Invalid opcode/script decoding crash



Any help would be hugely appreciated!

Thanks in advance,

Houssy.

 

[KushKings]

This mite help you..



The error you're seeing — Invalid opcode: 29184 — in a RuneScape Private Server (RSPS) client typically means that the client is trying to interpret something (usually a script or packet) that it's not programmed to understand, often due to a mismatch between the client and server.

Here's what might be causing the issue:​

1. Mismatch Between Client and Server​

• The opcode (29184) is not recognized by the client because the data it's receiving is not formatted the way the client expects.
• This often happens when you're using a client and server that are from different revisions or not properly synced in terms of cache or protocol.

2. Corrupt or Incompatible Cache​

• If your cache is outdated, corrupted, or doesn't match the one the server expects, opcodes and scripts can fail.
• Try deleting your current cache and letting the client re-download it, or verify you’re using the correct cache version.

3. Corrupted or Mismatched ClientScript​

• The error in ClientScript.method3475 suggests the script interpreter is failing — likely due to a malformed or unsupported script.

4. Custom Content or Poorly Packed Scripts​

• If you or someone else recently packed new scripts, especially client scripts (CS2 scripts), into the cache or edited opcodes, an improperly packed or buggy script could be causing the crash.

---

How to Fix It:​

Step-by-Step Suggestions:​

1. Check Your Client & Server Revision
   • Confirm that both are using the same revision (e.g., 317, 718, 742, etc.).
   • Mixing a 718 client with a 742 cache/server will cause issues like this.
2. Replace Cache
   • Delete your cache folder (often in C:/Users/YourName/.yourclientname/).
   • Restart the client to redownload the proper cache.
3. Debug Logging
   • Add debug statements around Class346.method4175 and ClientScript.method3475 to log the opcode or data it's trying to process.
   • It might help you identify the exact script ID or context.
4. Use a Known Working Setup
   • Try running the client and server setup from a clean, known-working source.
   • If it works there, compare the cache and code changes in your broken version.