Scrubbing off some things (like classes and level UI) from the displayables in 2k3?

[TenraiEmiko]

While this can be done easily in VXA and later by manipulating script files and adding scripts / plugins, I don't know how to do the removal of certain aspects (such as Classes and Level display) from displayables in 2k3...

Is there a way to do so in 2k3 (preferably no patches included so that it make sure the game would work with EasyRPG)?

Thanks!

 

[Andar]

you can't

as you said for yourself, RM2K(3) has no script access, and that would be the minimum to change the internally defined screens.

you can either completely skip the default screens and event your own menu (which takes a lot of experience in event commands), or you can program a patch doing what you want - which takes even more special knowledge on patch programming.

 

[Trihan]

The only way you could possibly do this outside of programming your own patch is using DynRPG by Cherry.

 

[TenraiEmiko]

you can't

as you said for yourself, RM2K(3) has no script access, and that would be the minimum to change the internally defined screens.

you can either completely skip the default screens and event your own menu (which takes a lot of experience in event commands), or you can program a patch doing what you want - which takes even more special knowledge on patch programming.

Well yeah, Grimm's Hollow has this kind of custom menu.

However, the part that I am pretty unsure is how to make custom stat gauges GUIs for such a menu...

 

[Andar]

It always goes completely over variables and show picture.

the simplest way for a gauge would be two pictures, one front picture of the empty gause and one back picture of the fill, with the position of the fill being more or less partially hidden behind the UI frame depending on how many % it is supposed to be filled.
That is basically mathematics - just a lot of mathematics.

 

[TenraiEmiko]

It always goes completely over variables and show picture.

the simplest way for a gauge would be two pictures, one front picture of the empty gause and one back picture of the fill, with the position of the fill being more or less partially hidden behind the UI frame depending on how many % it is supposed to be filled.
That is basically mathematics - just a lot of mathematics.

How much mathematics should it involve?

Will it go beyond basic things like comparing variable values and then add / subtract the X position / Y position of the bar's back image?

 

[Andar]

You'll need to get a percentage number of the fill from HP/MHP, then recalculate that percentage into the picture position of the fill.

less comparison but more multiplication/division and geometric formulae

 

[TenraiEmiko]

You'll need to get a percentage number of the fill from HP/MHP, then recalculate that percentage into the picture position of the fill.

less comparison but more multiplication/division and geometric formulae

BRUH.

"Geometric formulae"?

What are those in RM2k3's math functions, btw?