RPGJS Version 4.0.0 and RPGJS PlayGround

Samarium

RPGJS Version 4.0.0 and RPGJS PlayGround

RPGJS has just released its highly anticipated Version 4.0.0, packed with exciting new features and improvements. We're not stopping here. In this article, we'll take you on a journey through the roadmap of what's to come in RPGJS, promising an even more exhilarating experience for game developers and enthusiasts.

Roadmap

Enhancement of the Title-Screen Module

One of our primary focuses for the future is the enhancement of the title-screen module. We aim to make it more versatile and functional, ensuring it seamlessly integrates with a back office and Web3 technology. This enhancement will empower game developers to create captivating title screens while harnessing the power of external systems and blockchain integration.

Introducing the Web3 Module

In line with the latest advancements in technology, RPGJS is set to introduce a dedicated Web3 module. This addition will enable developers to explore the potential of blockchain technology within RPGJS games. Dive into the world of decentralized applications and create unique, blockchain-integrated gaming experiences for your players.

Research and Development for Game Performance

We understand that performance is a crucial aspect of any game. As such, we're investing in research and development to enhance the overall performance of RPGJS games. Expect improvements in frame rates, reduced load times, and an overall smoother gaming experience. Our goal is to provide both developers and players with top-notch performance.

Introducing the PlayGround (Beta Version)

https://playground.rpgjs.dev

In addition to our future plans, we're excited to introduce the PlayGround, currently in its beta version. The PlayGround is designed to help you get started with RPGJS and experiment with its capabilities. Here's what you can expect:

Continuous Example Updates: We'll regularly add new examples to the PlayGround, covering a wide range of RPGJS functionalities. These examples will serve as valuable learning resources for developers of all skill levels.
Open Source Initiative: Over the next few months, we plan to open-source the PlayGround. This move will make it accessible to the entire RPGJS community, encouraging collaboration and contributions to enhance the PlayGround experience.
Create Your Own Playground: In the near future, we'll enable developers to create their custom PlayGrounds and share them with others. This feature empowers you to showcase your RPGJS projects and share your expertise with the community.

dominx99

Wow it's so cool
Can't wait to play with the playground 😄

AsoStrife

I'm very happy to read that the stable version of RPGJS v4 has been released. I would like to add some notes in the hope that they can be useful for improving the project.

I believe the worst aspect of RPGJS is its documentation; it's really poorly done, and it's almost impossible to find answers to the questions one may have. Too many elements are taken for granted, and the documentation rarely provides a comprehensive example. PlayGround could be a very useful solution to this problem, and I hope to see the project evolve over time.

Some aspects that it would be interesting to explore further are:

GUI for character stats, abilities, etc. I've seen from the source code that these have been started but never completed.
Examples of battles or AI for monsters (monsters that follow you, attack you, let you escape after a certain number of steps, etc.).
Animations for various situations: abilities, events, etc.

I would like to participate more in the community by creating some web-based applications to simplify development, such as a database for objects, skills, and level design management, similar to what is already available in RPG-Maker.

With the evolution of PlayGround and the documentation, I should be self-sufficient enough to contribute to the community.

Samarium

Thanks for the feedback. I agree about the documentation. It's one of the reasons I decided to make RPGJS Playground.

RPGJS is very flexible and quite extensive for creating RPGs, the difficulty is to be able to add all the knowledge in a documentation and allow anyone to understand how it works.

gavinlaucn

Great Work!!!

gavinlaucn

It runs ok on pc, but when I open it with android phone with the url ,it gives the black screen.
The android browser info is:
UA: Mozilla/5.0 (Linux; Android 10; CLT-AL00 Build/HUAWEICLT-AL00; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/111.0.5563.116 Mobile Safari/537.36 XWEB/5279 MMWEBSDK/20230805 MMWEBID/2063 MicroMessenger/8.0.41.2441(0x28002951) WeChat/arm64 Weixin NetType/WIFI Language/zh_CN ABI/arm64

gavinlaucn

gavinlaucn It works in production mode.

Samarium

gavinlaucn

Thanks for the feedback. The playground is not intended to be functional on Android browsers 🙂

For the other points, I have noted the problems, thank you.

gavinlaucn

When I run yarn install.get the error.
76 timing command:ci Completed in 1447ms 77 verbose stack TypeError: Cannot read properties of null (reading 'pickAlgorithm') 77 verbose stack at Integrity.match (/usr/local/lib/node_modules/npm/node_modules/ssri/lib/index.js:273:24) 77 verbose stack at CachePolicy.satisfies (/usr/local/lib/node_modules/npm/node_modules/make-fetch-happen/lib/cache/policy.js:112:49) 77 verbose stack at Function.find (/usr/local/lib/node_modules/npm/node_modules/make-fetch-happen/lib/cache/entry.js:178:25) 77 verbose stack at async cacheFetch (/usr/local/lib/node_modules/npm/node_modules/make-fetch-happen/lib/cache/index.js:8:17) 77 verbose stack at async fetch (/usr/local/lib/node_modules/npm/node_modules/make-fetch-happen/lib/fetch.js:98:7) 78 verbose cwd /Users/gavin/Projects/e3-app/tmp/RPG-JS/packages/plugins/mobile-gui

gavinlaucn

gavinlaucn clean the yarn cache. It works.

gavinlaucn

When I run a vitetest get the error like this:
`ReferenceError: fetch is not defined
❯ Object.fetch packages/client/node_modules/@pixi/settings/src/adapter.ts:48:57
❯ Object.test packages/client/node_modules/@pixi/assets/src/detections/parsers/detectAvif.ts:16:45
❯ AssetsClass.init packages/client/node_modules/@pixi/assets/src/Assets.ts:318:37
❯ AssetsClass.load packages/client/node_modules/@pixi/assets/src/Assets.ts:433:13
❯ SceneMap.load packages/client/src/Scene/Map.ts:123:30
122| if (spritesheet?.resource) {
123| continue
124| }
| ^
125| Assets.add(tileset.name, spritesheet.image)
126| assets.push(tileset.name)
❯ RpgRenderer.createScene packages/client/src/Renderer.ts:185:23
❯ Object.next packages/client/src/Renderer.ts:256:10

This error originated in "tests/unit-tests/specs/sound.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "Sound is defined". It might mean one of the following:

The error was thrown, while Vitest was running this test.
This was the last recorded test before the error was thrown, if error originated after test finished its execution.`

gavinlaucn

gavinlaucn I change my node version to 18, It works.

gavinlaucn

I change my node version to 18, It works.

doogs

Hi @Samarium, really looking forward to the web3 module, in the meantime ive been playing around with v4. Thanks for the hard work!