mud-server | MUD server written in Java w | Game Engine library

by jnharton Java Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | mud-server Summary

mud-server is a Java library typically used in Telecommunications, Media, Media, Entertainment, Gaming, Game Engine applications. mud-server has a Permissive License and it has low support. However mud-server has 273 bugs, it has 5 vulnerabilities and it build file is not available. You can download it from GitHub.

A MUD server written in Java which aspires to be something of a general purpose framework for such games. For example, I have adopted the MUSH/MUCK convention of allowing exit names to be arbitrary text (rather than n/s/e/w), although there may be some support for reliably using the latter in the future (nothing explicity prevents creating exits with those names). Also, there is a fairly limited internal scripting system highly reminiscent of MPI from Fuzzball MUCK (Which is to say that it allows setting, modifying, and checking properties on each object. In general, though the code sticks closer to the hardcode end (at the moment) regard game systems and mechanics.

Support

Quality

Security

License

Reuse

Support

mud-server has a low active ecosystem.

It has 29 star(s) with 9 fork(s). There are 8 watchers for this library.

It had no major release in the last 6 months.

There are 12 open issues and 17 have been closed. On average issues are closed in 31 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of mud-server is current.

Quality

mud-server has 273 bugs (10 blocker, 3 critical, 231 major, 29 minor) and 4088 code smells.

Security

mud-server has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

mud-server code analysis shows 5 unresolved vulnerabilities (0 blocker, 0 critical, 0 major, 5 minor).

There are 95 security hotspots that need review.

License

mud-server is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

mud-server releases are not available. You will need to build from source code and install.

mud-server has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are not available. Examples and code snippets are available.

mud-server saves you 16617 person hours of effort in developing the same functionality from scratch.

It has 33030 lines of code, 2884 functions and 283 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed mud-server and discovered the below as its top functions. This is intended to give you an instant insight into mud-server implemented functionality, and help decide if they suit your requirements.

Command entry point
Called when a death is detected
Generates and returns the looted items
Calculates the damage of a given fighter
Reads a Spell object
Sets the surname of the class
Encodes the target string array into a binary ID
Runs the tool
Convert a string to a list of strings
Initialize the PC
Retrieve the list of players
Loads the book
Imports an area from a text file
Parse an integer representation of a string
Execute the spell
Reads the account data
Evaluate a list of strings
Returns a JSON representation of this field
Initialize members
Load item data
Load a list of strings
Drop an item from the database
Runs the command
Load an item data
Loads and returns the dialog
Deserialization

Get all kandi verified functions for this library.

mud-server Key Features

No Key Features are available at this moment for mud-server.

mud-server Examples and Code Snippets

No Code Snippets are available at this moment for mud-server.

Community Discussions

Trending Discussions on mud-server

websockify ws.send is not sending string to telnet server

QUESTION

websockify ws.send is not sending string to telnet server

Asked 2019-Mar-11 at 19:19

I have a telnet server running circlemud. I have websockify running as python proxying the connection. I can receive data as well as send data with the enclosed wstelnet.html that comes with websockify. However when I use the included simple.html file or the following code, it will receive data but will not send, or at least the telnet server never receives anything.

I am assuming the data I am receiving is blob, because that is the only way I can parse it. When you output the raw data to console it doesn't specify what data type it is. Also I am using the default Websocket api with my only include being jquery.

In the following I receive the message $('#message').html("asking for username"); as intended but the ws.send(blob); never sends anything, I have also tried just regular ws.send("test123"); to no avail.

...

ANSWER

Answered 2019-Mar-11 at 19:19

Make sure your client is sending line endings (i.e. ASCII character 10 or '\n') that the telnet server is expecting because it won't do anything with the text you sent until it sees a whole line.

Source https://stackoverflow.com/questions/54879320

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install mud-server

You can download it from GitHub.
You can use mud-server like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the mud-server component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: