1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Hey Guest, If you'd like to instant message with many other users, then join our
    Official Rune-Status Discord Server!
    Dismiss Notice
  3. Got your own Server? Looking for a Server to play right now??
    Make sure you check out the Public Server Directory!
    Dismiss Notice
  4. If you're new to the Rsps Scene and want to jump straight into learning how to Set-up and Customise your own RuneScape Private Sever then check out the Guides and Tutorials for RS2 here.
    Dismiss Notice
Dismiss Notice
Hey Guest,
Are you sure your posting in the Right Sections?
If your unsure which RuneTek version you are working with visit this page to find out.

Groovyc: unable to resolve class com.rs.game.player.Player

Discussion in 'Help & Requests' started by Kelvin, Nov 7, 2017.

  1. Hi.

    Could anyone help me out with this run error. Currently trying to launch this source (build 627) and this groovyc error is appearing. (intellJ IDE) Tried using google without finding any concrete answers.

    Thanks a lot for your attention

    Information:07.11.2017, 22.56 - Compilation completed with 4 errors and 0 warnings in 2s 69ms
    /Users/Kelvin/Desktop/Source/data/scripts/bootstrap.groovy
        Error:Error:line (9)Groovyc: unable to resolve class com.rs.game.player.Player
        Error:Error:line (10)Groovyc: unable to resolve class com.rs.script.ButtonScript
        Error:Error:line (13)Groovyc: unable to resolve class com.rs.script.ButtonScript
        Error:Error:line (22)Groovyc: unable to resolve class com.rs.game.player.Player
     
  2. Your compiler can't find the classes. In other words, you don't have all the files of the source in the correct locations.
     
  3. Indeed I find the file that are supposedly missing. But some classes seem to be duplicated, but with different contents

    [​IMG]
     
  4. Sir. An eye doctor. You must visit.
    l != r
     
  5. Yeah, those two files clearly. One is your PRayer class, and one is you PLayer class. That being said, Bart's answer is what you're looking for anyways. Put those files in the package locations defines and boom, no more error.
     
  6. Thank you. Got it working last night :-)
     
Loading...