Posts by Devidian

NOW FIRST OFFICIAL RELEASE: v0.1.5

https://github.com/Devidian/rw-plugin-oz-land-claim/releases

Remember also to install latest OZ - Tools from

https://github.com/Devidian/rw-plugin-oz-tools/releases

Patchnotes:

- feat: player gets message if area is renamed [0.1.4]
- refactor: now `/lc` opens the menu too (instead of doing nothing) [0.1.2]
- refactor: default area permissions adjusted [0.1.4]
- refactor: moved area3d methods to dedicated class [0.1.5]
- fix: missing translation for changing player permissions of a zone [0.1.1]
- fix: expanding area did not take origin permisssions into account [0.1.3]
- fix: Dropdown z-index issue workaround in PermissionPanel [0.1.3]
- fix: rename area now using direct SQL to Area db [0.1.5]
- fix: default-permissions in permissions panel from other area types are hidden now [0.1.5]
- fix: use `area.setName` before `Server.addArea`, `area.setPlayerPermission` after [0.1.5]
- fix: some more possible null pointer exceptions with area names [0.1.5]

+ Added more area permissions to set in Area permission window (resident,prisoner,exiled,friend and guest now available)

+ now there is a confirm dialog before splitting or expanding an area.

Splitting areas can now be tested, also fixed some bugs yesterday occuring when more than 1 player is actively using the plugin.

Known issues: if someone changes (adds/removes/expands/splits) areas, the area-frames are not updated on players that have them visible.

You are welcome, if you have any more trouble just write here or join my discord (see signature) then reply might be quicker. 😅

ok, good to know but for my LC plugin the player usually is in the zone that is released=destroyed. Maybe thats the same reason why set and the other methods are not working and throwing that exception. I'll try to get a workaround for that, thanks for the hint james.✅

area.destroy() is also causing NullpointerException red51 because area.INFINITE is null

hey, im sorry to hear you have any trouble. So im trying to help.

First your configuration:

- botEnable must be true

- botToken looks ok

- webHookEventUrl looks okay BUT events are only stuff like, weather changes, user interaction with objects

- at least you should set postStatus=true and setup webHookStatusUrl (can be the same webhook) then you see the bot enabled message

Then some more troubleshooting questions:

• is your bot in discord online?
  • if not did you check the server-logs?
• check general server log if Discord Connect and Tools plugins were loaded correctly
  • if you dont see any errors plugins sould be loaded
• check subdirectories in Logs directory starting with OZ.DiscordConnect if you find any errors.

Area expansion is now ready for testing.

fixed: chat commands are now case insensitive, `/lc help` now shows `/lc open` command.

Gerne, der Server ist 24/7 offen. Ingame chat wird nach discord übertragen, kann ich also auch immer lesen Und wer mag kann auch mitlesen. http://discord.gg/8h3yhUT

Hey there,

before the great shutdown (when unity version was announced) i already started to create my own LandClaim plugin as i was not satisfied with the areaprotection we were using in the Java version. But as i did with all my (planned) plugins i stopped working on it.
When i setup my unity server i tried some existing plugins but they were not working as expected, so i started with my own plugin again. It is still not 100% where i want it to have but the main features needed as MVP are working so far.
So i want to invite some players to test it on my public development Server. The server is called

Omega Zirkel - Plugin development & Testing, current test: OZ LandClaim

NOW FIRST OFFICIAL RELEASE:

https://github.com/Devidian/rw-plugin-oz-land-claim/releases

Remember also to install latest OZ - Tools from

https://github.com/Devidian/rw-plugin-oz-tools/releases

====================================================================================================

I recommend to bind the command `/lc open` to a key or mouse, this is almost everything you need to do using it.

Current features:

• Claiming by players themself based on Chunks
  • Players have a basic claim limit (can be configured)
  • Players get more claims if they have more playtime on a server (rate configured by admins)
  • Players have to stay a configurable time in a chunk before they can clime (prevents new players to grief areas
    • (Planned: "soft decay" of chunks / protection based on playtime)
  • Players can turn on "chunk view" where they can see chunks
    • Current view: shows the current chunk borders in yellow
    • Owned view: shows the chunks owned by the player in green
    • Other view: shows chunks owned by others in blue (and other colors in the future)
      • (Planned: color for special areas, areas for sale, pvp areas?)
  • Players that claim a chunk become "owner" of that chunk
    • all other players are "guests" by default
  • Players can give other players different permissions for their claim
    • Resident: mostly the same rights as owner in the area but cant change area stuff
    • Friend: can build and destroy own stuff, cant terraform, can use chests
    • Guest: default level, can enter and leave the area but has no overall rights
    • Prisoner: you need slaves? this is the permission you need, but they cant do anything (like guests that cant leave)
    • Exiled: someone is unwanted? exile him!
  • Players can release their claims - if they don't want it anymore (!anyone else can claim then)
  • Players can rename their claims
  • Players can expand claims (i don't want to have a 3 by 3 area of 9 single area chunks, i want to have a single big area 3 by 3 )
    • Claims can be expanded up,down,north,south,west,east
    • expansion will respect claim limits and time in chunks but it will sum up all time so you only need to stay in one chunk)
    • you cant expand if a chunk in direction is claimed by other players
  • Players can split claims with more than 1 chunk into single-chunk claims
• Admins can change permissions on any claim
• Admins can release any claim
• Admins can rename any claim
• Admins don't have claim limits (configurable)
• Admins don't need to wait to claim (configurable)
• Admins can create special areas with special permissionsets
  • rest-area (resting area with no hunger and thirst, no pvp etc.
  • pvp area
  • trap area (go in and never find out (Jail)
  • general special area (name public places block areas from claiming)
• Other features:
  • Plugin is fully translated to german + English, more languages possible (just ask)
  • An overlay shows up current chunk status and time needed to claim
  • Claimed areas will work even if plugin gets uninstalled as it uses ingame area functionality
  • Connections to discord for claim/release announcements using my Discord Connect Plugin (optional feature, no need for Discord Plugin)
  • In game announcements
  • confirmation window when expanding, splitting or release areas to avoid mistakes

Features in progress (what im still working on) before i release first version to public

• currently only bugfixing

Features planned after first release:

• Players can sell their claims to other Players (first version wont use any currency, i plan to create a seperate plugin for that)
  • other players can buy claims if they have enought free claims
  • selling and buying will be announced ingame (and optional in discord)

Screenshots:

Now is the best time to test and give any feedback. Hope to see anyone testing next days.

Best regards
Devidian

PS: You are welcome to join my Discord if you speak english or german if you need any live support with my plugins or have any feedback. => http://discord.gg/8h3yhUT

I'm currently working on my own LandClaim plugin and noticed some things:

- if you use `area.setPlayerPermission` before `Server.addArea`, the permissions are not persisted to the database.
- if you use `Server.removeArea` before removing all player permissions from the area, the permissions stay in the database with no valid area.

Might not be critical but it cost me much time to figure this out

Just noticed there is no hoverStyle.borderWidth.set shortage (and others), so i wrote an extend to UIElement with some helpers.

/**
 * extends UIElement with some helper methods missing from UIElement
 */
public class OZUIElement extends UIElement {
    public void setHoverBorderColor(int rgba) {
        hoverStyle.borderBottomColor.set(rgba);
        hoverStyle.borderLeftColor.set(rgba);
        hoverStyle.borderRightColor.set(rgba);
        hoverStyle.borderTopColor.set(rgba);
    }

    public void setHoverBorderWidth(float thickness) {
        hoverStyle.borderBottomWidth.set(thickness);
        hoverStyle.borderLeftWidth.set(thickness);
        hoverStyle.borderRightWidth.set(thickness);
        hoverStyle.borderTopWidth.set(thickness);
    }

    public void setHoverBackgroundColor(int rgba) {
        hoverStyle.backgroundColor.set(rgba);
    }
}

Works on my servers too, even if triggered by discord slash command.

I can confirm this, its funny

yes it seems so, i did it too, marked it as workaround in the comments. For now its ok to work with.

BTW this is my method to create the area:

    /**
     * Converts a chunk coordinate into an Area
     */
    public static Area getVirtualAreaFromChunkVector(Vector3i chunkPosition) {
        Vector3f chunkOrigin = new Vector3f(chunkPosition.x * 32, chunkPosition.y * 64, chunkPosition.z * 32);
        Vector3f chunkMax = new Vector3f(chunkOrigin.x + 31.999f, chunkOrigin.y + 63.999f, chunkOrigin.z + 31.999f);
        Area area = new Area(chunkOrigin, chunkMax);

        area.setName("Chunk " + chunkPosition.toString());
        area.setNameVisible(true);
        area.setDefaultPermission("ozlc-guest");
        return area;
    }

And i call it like this:

    @EventMethod
    public void onPlayerEnterChunkEvent(PlayerEnterChunkEvent event) {
        Player player = event.getPlayer();
        Vector3i oldChunkPos = event.getOldChunkCoordinates();
        Vector3i chunkPos = event.getNewChunkCoordinates();

        logger().debug("Player " + player.getName() + " entered chunk " + chunkPos.toString()
                + " from chunk " + oldChunkPos.toString());

        chunkClaimUtil.leaveChunk(player, oldChunkPos);
        chunkClaimUtil.enterChunk(player, chunkPos);

        // if player has "showVirtualAreaFrame" enabled, show chunk area
        if (player.hasAttribute("showVirtualAreaFrame")) {
            Area area = ChunkClaimUtil.getVirtualAreaFromChunkVector(chunkPos);
            updateVirtualAreaFrameForPlayer(player, area);
        }
    }

Some exceptions i got while testing:

java.lang.NullPointerException: Cannot read field "handle" because "net.risingworld.api.objects.Area.INFINITE" is null
    at net.risingworld.api.objects.Area.destroy(Area.java:393)

java.lang.NullPointerException: Cannot read field "handle" because "net.risingworld.api.objects.Area.INFINITE" is null
    at net.risingworld.api.objects.Area.setStartPosition(Area.java:307)

java.lang.NullPointerException: Cannot read field "handle" because "net.risingworld.api.objects.Area.INFINITE" is null
    at net.risingworld.api.objects.Area.set(Area.java:328)

Im not sure (joking) but a public static final field should not be NULL ? red51

The docs say addGameObject should not be called so often, so i tried to update the Area3D object but it seems not to update it actually

    public void updateVirtualAreaFrameForPlayer(Player player, Area area) {
        Area3D chunkBorderArea = ((Area3D) player.getAttribute("virtualAreaFrame"));
        if (area == null) {
            if (chunkBorderArea != null) {
                player.removeGameObject(chunkBorderArea);
                player.deleteAttribute("virtualAreaFrame");
                player.sendTextMessage("debug:> virtualAreaFrame removed");
            }
            return;
        }
        if (chunkBorderArea == null) {
            chunkBorderArea = new Area3D(area);
            // chunkBorderArea.setAlwaysVisible(true);
            chunkBorderArea.setColor(borderColor);
            chunkBorderArea.setFrameColor(frameColor);
            chunkBorderArea.setFrameVisible(true);
            player.setAttribute("virtualAreaFrame", chunkBorderArea);
            player.addGameObject(chunkBorderArea);
            player.sendTextMessage("debug:> virtualAreaFrame added");
        } else {
            // Nullpointer exception on setStartPosition
            // Area current = chunkBorderArea.getArea();
            // current.setStartPosition(area.getStartPosition());
            // current.setEndPosition(area.getEndPosition());
            // chunkBorderArea.setArea(current);
            chunkBorderArea.setArea(area);

            player.sendTextMessage("debug:> virtualAreaFrame updated");
        }
    }

Its for my current plugin im working on Land Claim - (i started it for the Java version but never finished it before the unity news).

Its an option to turn on borders of the current chunk, if the player moves to another chunk with active option the virtual border is updated to the chunk he enters.

The player does not need to set any area, its calculated from the chunk he enters, so in theory the tool is not even needed but if i do not activate it, the area is not shown.

Your way is good to know but i think i would have to (re)move it somehow if the player moves or disables this feature.

edit: Ii just walked through the javadoc, maybe i can use setAttribute to store a ref to the area3d too, so i can update it on change or remove it precisely.

Hey i currently try to show a virtual area but its not what i like it should be....

Ok first i tried

player.enableAreaSelectionTool(false);

player.setAreaSelectionData(area);

but i dont want to have the selection tool activated, just show the area. If i then call

player.disableAreaSelectionTool();

the selection is invisible again... i tried many things but could not get it as i like it.

Only once it closely behaved like i wanted it, but that was after many plugin reloads and gm switches.
After relog it was not behaving like i wanted it again.

UPDATE:

I've managed to to a trick to get it working like i want it to:

                    if (!player.hasAttribute("selectionToolHack")) {
                        player.setAttribute("selectionToolHack", true);
                        player.enableAreaSelectionTool(false);
                        player.enableAreaSelectionTool(false);
                        player.disableAreaSelectionTool();
}

If i call enable twice and disable afterwards the visibility seems to stay but the selectiontool stays disabled. This is not as elegant as i was looking for but still its working for now. I only need to do this hack once a session so i added a player attribute.