Jump to content

Scyllas Rock (Beta)


Scyrizu

Recommended Posts

Scylla's Rock is gearing up for a large update this spring, revamped new player welcome areas, application process, cosmetics (including dancing armor stands, particle effects, join/leave messages, and much more).

 

1.18 support is expected to be released for new chunks March 20, 2022, as well as a world border expansion for new areas to be generated in.

Beta is expected to end on June 21, 2022. This will include a new world!

OGQtQgN.png

 

We're looking for beta players as well as a full staff team including:

 

We're looking to recruit a full staff team including

  1. Developers ( Player)
  2. Lead Developer (Player)
  3. Web developers ( Player)
  4. Community Managers / Event Planners ( Player)
  5. Marketing staff ( Player)
  6. Admins (Player)
  7. Moderators ( Player)
  8. World painter ( Player, but may not complete a lore quest first nor assist others)
  9. Builders ( Player)
  10. Lore-Writers ( Player, but may not complete a lore quest first nor assist others)
  11. Entity Designer ( Player)
  12. Artist ( Player)

 

Quote

To apply join our please first post your application on this forum using the template provided below. Next join our discord, fill out a player whitelist application using our google forum, and notify @whitelist that you've posted on this forum. Those who do not follow these directions will not be considered for staff.
 

Spoiler

IGN

AGE

TIMEZONE

POSITION APPLIES FOR

WHY WE SHOULD CONSIDER YOU OVER OTHER CANDIDATES

PORTFOLIO IF APPLICABLE

 

 

Check out our Discord: https://discord.gg/xSkanQb6Kn

 

Why us?

Our project is entirely Non-For-Profit, meaning we're not trying to scam players into buying crazy loot-boxes or wasting their money. We hope to build a real, sustainable, and healthy community. Additionally, we've been in beta for almost a year now, and aren't going anywhere!
Our staff is a team, and we listen to each-other and our community to make decisions and decide what direction to take the server.

For all staff, I have agreed to assist our lead developer with my own skill set by offering all staff resume reviews and mock interviews - I am a graduate student in a relevant field (IO Psychology & MBA dual major) as well as having worked as a recruiter.

 

f2Zyovn.gif

For those who code Java or C for the server, our lead developer has offered to do code review or answer questions for those looking to learn or improve! He's a talented Computer Science major and very patient.

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Hello everyone, I'm making this post to seek help for my modded block, It's a special block called FrozenBlock supposed to take the place of an old block, then after a set amount of ticks, it's supposed to revert its Block State, Entity, data... to the old block like this :  The problem I have is that the system breaks when handling multi blocks (I tried some fix but none of them worked) :  The bug I have identified is that the function "setOldBlockFields" in the item's "setFrozenBlock" function gets called once for the 1st block of multiblock getting frozen (as it should), but gets called a second time BEFORE creating the first FrozenBlock with the data of the 1st block, hence giving the same data to the two FrozenBlock :   Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=head] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@73681674 BlockEntityData : id:"minecraft:bed",x:3,y:-60,z:-6} Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=3, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=2, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} here is the code inside my custom "freeze" item :    @Override     public @NotNull InteractionResult useOn(@NotNull UseOnContext pContext) {         if (!pContext.getLevel().isClientSide() && pContext.getHand() == InteractionHand.MAIN_HAND) {             BlockPos blockPos = pContext.getClickedPos();             BlockPos secondBlockPos = getMultiblockPos(blockPos, pContext.getLevel().getBlockState(blockPos));             if (secondBlockPos != null) {                 createFrozenBlock(pContext, secondBlockPos);             }             createFrozenBlock(pContext, blockPos);             return InteractionResult.SUCCESS;         }         return super.useOn(pContext);     }     public static void createFrozenBlock(UseOnContext pContext, BlockPos blockPos) {         BlockState oldState = pContext.getLevel().getBlockState(blockPos);         BlockEntity oldBlockEntity = oldState.hasBlockEntity() ? pContext.getLevel().getBlockEntity(blockPos) : null;         CompoundTag oldBlockEntityData = oldState.hasBlockEntity() ? oldBlockEntity.serializeNBT() : null;         if (oldBlockEntity != null) {             pContext.getLevel().removeBlockEntity(blockPos);         }         BlockState FrozenBlock = setFrozenBlock(oldState, oldBlockEntity, oldBlockEntityData);         pContext.getLevel().setBlockAndUpdate(blockPos, FrozenBlock);     }     public static BlockState setFrozenBlock(BlockState blockState, @Nullable BlockEntity blockEntity, @Nullable CompoundTag blockEntityData) {         BlockState FrozenBlock = BlockRegister.FROZEN_BLOCK.get().defaultBlockState();         ((FrozenBlock) FrozenBlock.getBlock()).setOldBlockFields(blockState, blockEntity, blockEntityData);         return FrozenBlock;     }  
    • It is an issue with quark - update it to this build: https://www.curseforge.com/minecraft/mc-mods/quark/files/3642325
    • Remove Instant Massive Structures Mod from your server     Add new crash-reports with sites like https://paste.ee/  
    • Update your drivers: https://www.amd.com/en/support/graphics/amd-radeon-r9-series/amd-radeon-r9-200-series/amd-radeon-r9-280x
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.