RunUO Community

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[RunUO 2.0 RC1] Xanthos Claim 1.6

Nam01

Wanderer
[RunUO 2.0 RC1] Xanthos Claim 1.6

All credit goes to Xanthos for making this script all i did was edit it For Runuo 2.0

Put the claimconfig XML file in the data folder and the rest of file into custom file

Then restart your server should be good to go.

Claim works on mine

here is original thread for those of you who asked for it

http://www.runuo.com/forums/showthread.php?t=64269&highlight=Xanthos
 

Attachments

  • Xanthos Claim.rar
    15.2 KB · Views: 392

Vhaerun

Sorceror
Uhm. Exactly what system is this? I am guessing it's a [claim command system that will give tokens and/or gold? Could you post a link to the original thread so we know which script this one is actually an update for? Thanks.
 

Dravin

Wanderer
Hi, I am new to all of this, but have managed to search out the answers to most of my questions up until now. I apologize in advance if this question has already been answered somewhere and I just didnt fiind it.

I just installed this script from Xanthos, and got the following errors in my server..

Code:
RunUO - [www.runuo.com] Version 2.0, Build 2357.32527
Core: Running on .NET Framework Version 2.0.50727
Scripts: Compiling C# scripts...failed (2 errors, 0 warnings)
Errors:
 [COLOR="Red"]+ Xanthos/Claim/Claim.cs:
    CS0246: Line 45: The type or namespace name 'CommandEventArgs' could not be
found (are you missing a using directive or an assembly reference?)
    CS0246: Line 58: The type or namespace name 'CommandEventArgs' could not be
found (are you missing a using directive or an assembly reference?)
    CS0246: Line 128: The type or namespace name 'CommandEventArgs' could not be
 found (are you missing a using directive or an assembly reference?)
 + Xanthos/Xanthos/Utilities/findMobs.cs:
    CS0246: Line 93: The type or namespace name 'CommandEventArgs' could not be
found (are you missing a using directive or an assembly reference?)
    CS0246: Line 110: The type or namespace name 'CommandEventArgs' could not be
 found (are you missing a using directive or an assembly reference?)[/COLOR]
Scripts: One or more scripts failed to compile or no script files were found.
 - Press return to exit, or R to try again.

Is this something that is needed from a support script, or a portion of another script that I dont have? Could it have something to do with the 'auction script' that it mentions in the readme, but it doesnt say is a mandatory installation.. if so could I just comment out the offending lines and hope that the script runs within expectations?
Once again I apologize if this question has already been answered.
 
I got the same error. Can someone help?

Code:
RunUO - [www.runuo.com] Version 2.0, Build 2357.32527
Core: Running on .NET Framework Version 2.0.50727
Scripts: Compiling C# scripts...failed (2 errors, 0 warnings)
Errors:
 + Custom/Claim/Claim.cs:
    CS0246: Line 45: The type or namespace name 'CommandEventArgs' could not be
found (are you missing a using directive or an assembly reference?)
    CS0246: Line 58: The type or namespace name 'CommandEventArgs' could not be
found (are you missing a using directive or an assembly reference?)
    CS0246: Line 128: The type or namespace name 'CommandEventArgs' could not be
 found (are you missing a using directive or an assembly reference?)
 + Custom/Utilities/findMobs.cs:
    CS0246: Line 93: The type or namespace name 'CommandEventArgs' could not be
found (are you missing a using directive or an assembly reference?)
    CS0246: Line 110: The type or namespace name 'CommandEventArgs' could not be
 found (are you missing a using directive or an assembly reference?)
Scripts: One or more scripts failed to compile or no script files were found.
 - Press return to exit, or R to try again.

*edit nm I found this elsewhere on boards. Adding using Server.Commands at top solve the issue
 
Top